The issue we are facing is whenever we run `python manage.py migrate` after cloning the repo/pulling the repo, it takes around 30-50 mins.
Ask HN: What's your development environment in your startup using Django?
1–7 of 7 posts
Re: Ask HN: What's your development environment in your startup using Django?
#2Re: Ask HN: What's your development environment in your startup using Django?
#3The title is general, but your post question is extremely specific. You should change the title.
Re: Ask HN: What's your development environment in your startup using Django?
#4Re: Ask HN: What's your development environment in your startup using Django?
#5Then if you want to load the database we have a shell script wrapper that can do a few things.
Load an sql from an s3 private bucket to refresh your local database, so even if you crash anything you can always fix things with a quick shell command. We also tie things into newrelic and sentry to help us debug code locally before it even gets to sandbox or prod.
Re: Ask HN: What's your development environment in your startup using Django?
#6Are you collapsing your migrations?
Unless you need to maintain multiple production environments with different versions of your software you should be doing so with some regularity.
Re: Ask HN: What's your development environment in your startup using Django?
#730-50m for ./manage.py migrate seems way too long. Are you collapsing your migrations? Unless you need to maintain multiple production environments with different versions of your software you should be doing so with some regularity.