Skip to content

api of a blog, following clean architecture, separation of responsibilities, relationships between tables, and user authentication

License

Notifications You must be signed in to change notification settings

hebertsanto/API-blog

Repository files navigation

Api overview

This API was made to improve my knowledge of clean architecture and I learned a lot.

System features

  • Create a user.
  • Log the user in by generating an access token.
  • User can create posts
  • User can delete posts
  • User can edit posts
  • User can get a post by its id
  • List all posts by a user
  • User can search posts
  • Users related to your posts
  • Add comments to posts
  • Delete a comment
  • Pick up a comment
  • Edit a comment
  • List all comments on a post, if any
  • User can add tags to posts
  • User can add photos to their posts
  • It is possible to sort posts by tags
  • User can add categories to posts
  • User can have a profile
  • User can edit their profile
  • User can deactivate their account
  • User can delete their account
  • User can reset their password

I tried to maintain a cool and well-organized architecture, I intend to improve this project because it was something I enjoyed doing, I focused a lot on the directory structure of this application, it was the first time I I organized a project like this, so if you have any tips for improvement, don't hesitate to call me to talk. Here on my profile you have all my social networks.

Technologies used in this project

  • node js
  • typescript
  • express
  • eslint
  • prettier
  • commitlint
  • husky
  • prisma
  • postgres
  • postman
  • jest
  • git
  • nginx
  • github actions

Data modeling

Captura de tela de 2024-05-21 22-41-51

Contact