HTTP-APIs
Add to the documentation how to handle ApiDoc/schema changes
I'm submitting a
- [X] feature request.
Current Behaviour:
We have alembic installed but there is no mention in the documentation about how to create the first migration nor an automatic mechanism todo migration when the ApiDoc changes.
Expected Behaviour:
When the hydrus instance is run for the first time, a migration file should be created with the initial database schema. Every time a change happens on the ApiDoc that affects the database, the "migrate" command should be run to write a new migration version.
I'm submitting a
- [x] feature request.
Current Behaviour:
We have
alembicinstalled but there is no mention in the documentation about how to create the first migration nor an automatic mechanism todo migration when the ApiDoc changes.Expected Behaviour:
When the hydrus instance is run for the first time, a migration file should be created with the initial database schema. Every time a change happens on the ApiDoc that affects the database, the "migrate" command should be run to write a new migration version.
Hi can you specify clearly what we have to do i'll add this to my current PR
it is not advisable to provide different feature in the same PR, please open another one.
Are you familiar with alembic and database schemas?
Hi i am new to this open source stuff can i get assign for this issue ? Can you please tell me what I have to learn for solving this issue?
