search

DelegateIt / OrderAPI

The backend API for all of the DelegateIt clients
3 stars 0 forks source link

Versioning and Migration #80

Closed georgeaf99 closed 8 years ago

georgeaf99 commented 8 years ago

The branch is essentially ready to be merged into master, all that is missing are the migrations needed for the production models (we can commit this after merging into master). All previous migration code will be completely replaced.

Once this is merged master will not be production capable. At least until we migrate the db and add versions to items.

xuset commented 8 years ago

Is there a way we can prevent the "master will not be production capable" thing?

georgeaf99 commented 8 years ago

Not really; however, once we merge this branch into master we will be able to migration the production database (w/ the migration tool from 360a258) to use versions.

xuset commented 8 years ago

I think it's good practice to always keep master production ready. I honestly don't see any technical limitations as to why we can't do whatever migration needs to be done then merge it into master, or am I missing something?

georgeaf99 commented 8 years ago

Yeah, we could run the migrations before we merge. I am only being hesitant because I'm afraid we might break something by adding the version field to all db items.