[Question] Creating migrations for easier migrating the application

[DmytroLitvinov]

Hi there,
I see that migrations are not created in repo and for me as a Django developer this is kind of unusual.
Is there any reason behind that decision and how do you plan to support this one?

Having migrations commited into repo would allow everyone to have same provisioned database and it will allow easier to migrate and apply fixes in schema.

[horilla-opensource]

Hi @DmytroLitvinov ,

We initially planned to remove migrations from the repo to open developers to have customisations within the module itself as we started with function based views in our version 1. But it came out to be bad decision from our end and when many people started using that we were not able to incorporate it into the version 1.

But in our version 2 and our CRM we are adding the migrations file along with repo for easily deployments and uniform schema with the introduction of class based views into the codebase.

We deeply regret our move of not using the migrations in our version 1 and we are rectifying that mistake in our version 2.

With Regards,
Team Horilla

[DmytroLitvinov]

Hi Team Horilla,
Thank you for your detailed explanation. It gave me a full context.

Btw, in case you plan to give flexability to users, maybe it makes more sense to create a feature called "user defined fields" for models which you have in applicaiton.

Also, do you know if v2 is ready to use or any plan when it can be released?