Add to the documentation how to handle ApiDoc/schema changes

[Mec-iS]

I'm submitting a

• 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.

[Krish-bhardwaj]

I'm submitting a

• 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.

Hi can you specify clearly what we have to do i'll add this to my current PR

[Mec-iS]

it is not advisable to provide different feature in the same PR, please open another one.

Are you familiar with alembic and database schemas?

[Wansh619]

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?

[Mec-iS]

@Wansh619 https://www.hydraecosystem.org/Starting-Material

[Wansh619]

Thank and if i need more resources i will tell you.

[arneja-arnav]

Hey. has this issue been resolved?
Would love to work on it