Patricio Cano
Patricio Cano
I have decided against using JWT tokens for authentication. Use [Pow](https://hexdocs.pm/pow/README.html#installation) instead.
In order for v1.0 to be commercially viable, we need to have proper admin features, with reporting tools, maybe even instrumenting as well. We need ways to manage users, manage...
Settings that could be changed without having to restart or re-deploy the app should be stored in the DB. We need a module, and admin views for that.
We should be able to have "Organizations" within AlloyCI, to group projects together, and allow admins of the organizations a better overview of their projects. - [ ] Add orgs...
Related to #51 Right now we are accessing the repositories to show under `New Project` via the user's OAuth token. This has the following implications: - Repos from organizations that...
GitHub recently introduced the CheckSuite API: https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/ https://developer.github.com/v3/checks/ It would be perfect for AlloyCI to take advantage of this new feature. Even though inline comments might not be possible as...
Build outputs are hugely verbose right now. Maybe we should filter boilerplate stuff, specially git related action, and maybe the `before_script` output, unless there is failure there. This could be...
Users should be able to make sure their config file is correct. A linter should allow them to find any errors.
Docker and kubernetes have become so widespread that a lot of build pipelines depend on them for deploying and orchestrating. We should provide a Docker registry that would allow users...
The code should be documented using heredoc, and if possible, available via hexdocs