django-pghistory icon indicating copy to clipboard operation
django-pghistory copied to clipboard

Commands to generate and apply django migrations for development purposes

Open quevon24 opened this issue 2 years ago • 1 comments

I added two useful commands to makefile to be able to generate and apply migrations manually

I got to this since when implementing the new tracker in PR #85 I had the need to generate new migrations to be able to run the tests.

quevon24 avatar Mar 23 '23 19:03 quevon24

@quevon24 a little context here - There are quite a few other libraries in opus10, all of which have the same Makefile that's provided by a common template here. So ideally this change would go there so I can synchronize it everywhere else and keep the scaffolding of all projects in sync. I use footing to do this.

On a higher level, the Makefile was mostly intended to be a wrapper around CI. If you want to run an arbitrary dev command, you can do make shell first to get a shell and then run any command.

Perhaps it would be better to just change the docs like you did so that users know about make shell?

PS I always use make conda-setup and activate the env so that commands all work natively. I've just started to avoid docker-based development these days. Did you find it convenient to use the docker-based commands to run the code? Have you ever tried conda to manage python envs and virtualenvs? Just curious how many others use it. I've grown to like it

wesleykendall avatar Mar 27 '23 02:03 wesleykendall