I don't want to bug the OpalStack staff while they're so busy with the onslaught of WebFaction customers this week, so I thought I'd see what advice I can get from the community at large…
I have a Django application with uWSGI and PostgreSQL on my shared-hosting-plan account. Since my projects are mostly just for fun, up until now I've done all my development "live" on the server. But I'd like to establish a separate development environment, preferably local, where I can work on the code and then release it to production when it is ready—if for no other reason than just to establish the habit.
My thought was to create a version-control repository from my existing production code on the server, which I could then check out to my machine, edit locally, and push back to production when appropriate.
My Django code, templates, static files, etc. seem straightforward enough to add to a repo, but how do I handle the database? One of the reasons I chose Django and OpalStack was because they almost completely abstract away the DB layer, so it's all pretty opaque to me. I'm not even sure I know enough to know what it is that I am asking.