An usefulness API is an API with some basic (important) features, like user connexion, setted database and Docker ready. Every projects have to be developped in TDD.
It's like a boilerplate to set up a project quickly.
- User connexion/registration
- Using a database with migration possibilities
- Docker ready
- A dev environment already configured (editor, lint, travis, code coverage)
A great and flexible development environnement is important. It's important also to quickly integrate other developers. When manage database, it should be easier to handle database migrations.
The main feature is user connexion and ability to register some new user. This should create authentication using tokens.
Docker or container solutions are great to allow you flexibility and speed when you deploy your apps.
Never hesitate to contribute to the follow repositories. Submit issues, comments and PRs !
You can also create your own repositories. To create a better usefulness API, you should have to develop in TDD.
- usefulness-api-phoenix
- usefulness-api-expressjs
- usefulness-api-expressjs-reasonml
- usefulness-api-zf3 (not ready)
- usefulness-api-laravel
- Just Pull Request never ninja merge or whatever solutions you did to quick fix any mess or dev. You should create only one commit per feature, that's the reason you have to create a PR when adding your code with multiple commits. This allows you to get a clean history.
- Your commits should say something important.
- If you are using Travis always wait the green bullet, even if its' trivial, otherwise why use travis ??