- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API for codecarbon #145
API for codecarbon #145
Conversation
Update Solution Carbon
Merge pull request #1 from mlco2/master
Adding repository to emissions persistence router
* refacto: extracting server as standalone package, api test setup (example on one router) * feat: in memory emissions repository tests (to test the interface) Co-authored-by: Amine Saboni <asaboni@octo.com> Co-authored-by: benoit-cty <6603048+benoit-cty@users.noreply.github.com>
…rg in memory repo tests
Merge pull request #160 from mlco2/api_refacto_repositories
@SaboniAmine Why the database model is in models.py is in the "domain" folder instead of "database" folder ? I've read Octo blog https://blog.octo.com/application-domain-infrastructure-des-mots-de-la-layered-hexagonal-clean-architecture/ ;) I will put Alembic file in database, is it ok ? |
run carbonserver with docker-compose
Modifications of API Database Merge pull request #168 from mlco2/api_db
Api routers testing
Finally good for me, sorry for the delay. |
We build an API for CodeCarbon that allow to store emissions in a database.
The model used is:
Main packages used:
TODO before merge :