On Sunday, July 28, 2019 at 2:35:03 PM UTC-7, David Grant wrote: > > > I'm using Google AppEngine and I have no access to the server. The > alternative is to have the exact same code checked out on my local machine. > Connect to the remote database with a special proxy tool that google > provides (so the db becomes available on a local port) and then run the > migrations. Problems with this are: 1) Hitting the remote database via the > proxy is extremely slow, like ridiculously slow and 2) there is a chance I > have the wrong local code. ie. this could mean I run some extra migrations > or not run enough migrations, thus causing production to be broken. > > I guess I can do this as part of the deploy, which makes the version is guarenteed to be the correct one. But I still need to use the google cloudsql proxy which sucks.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9ab39c2b-503c-44ff-89f3-bb5203ab799c%40googlegroups.com.
