This is the backend repository of SnippetServe, a place for developers to share and re-use code snippets with ease
Made with: ๐ฅ NodeJs ๐ฅ ReactJs
Note: You can find the frontend in the frontend repo
- Clone this repo
git clone https://github.com/SnippetServe/backend - Install all the packages required:
yarn install - Create a new file under root of this project called
.env. Add properties as mentioned in.env.example. You need a Postgres DB running. - Now run
yarn devRun, this will start nodemon as well, so even if you change any code, it will automatically compile. - For production use
yarn start
- Typescript
- Nodejs
- Expressjs
- TypeORM
- Postgresql
- Clone or fork this repo.
- Run
yarn installto install all dependencies. - Create a .env file if it doesn't exist or change the existing one with your postgres db url.
- Pick up an issue or a card from the trello board (need to be added to access it). Create a new branch named
trello-id/feature. For example235x53/oauth-implementation - After you have made changes, make sure that
yarn lintandyarn builddoesn't throw any errors andyarn devRunworks as expected. - If
yarn lintthrows any errors you can autofix most of these errors by runningyarn lintFix. If errors persist even after this, then you have to manually fix these. You can use vscode to do so. Just hover over the error and vscode will show you a suggestion(ctrl + .also works on windows). - Now commit your changes and push to the above branch that you created and then raise a PR to master.
- You will need at least 2 approvals before your changes get merged into master.
๐ Found a issue or bug? Feel free to open a issue ๐
๐ฅ Have a feature in mind? Feel free to submit a pull request ๐
We can maybe use SemVer for versioning. Coming soon.
All you need is the above-mentioned .env file. Create one and copy in the content from .env.example. Change the DATABASE_URL with your own database.
For development environment the JWT_SECRET can be the same as the example, for production change with an appropriate one.
Coming soon?
Coming soon a description of the api, including authentication methods as well as explaining all the endpoints with their required parameters.
Please take a look at Our License