This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sudo groupadd docker | |
sudo usermod -aG docker $USER | |
su - $USER | |
# log out and log in again to make these changes effective |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# REST API Naming Guidelines | |
API routes should typically be named using nouns rather than verbs. | |
This aligns with the principle of using HTTP methods (verbs) like GET, POST, PUT, DELETE, etc., to perform actions on the resources represented by the nouns. | |
## Some guidelines for naming API routes | |
1. Use nouns: Name your API routes after the resources they represent. For example, if you have a resource representing users, the route could be /users. | |
2. Use plural nouns for collections: When dealing with collections of resources, it's a convention to use plural nouns. For example, /users for a collection of users, /posts for a collection of posts, etc. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
├── src | |
│ ├── main | |
│ │ ├── java | |
│ │ │ └── com | |
│ │ │ └── example | |
│ │ │ ├── adapters | |
│ │ │ │ ├── controllers | |
│ │ │ │ │── database | |
│ │ │ │ │ ├── postgresql # Implementation for PostgreSQL | |
│ │ │ │ │ │ ├── entities # PostgreSQL entity classes |
OlderNewer