Re: Django development workflow

> "Clifford" == CLIFFORD ILKAY writes: Clifford> It's entirely up to you. You could use your database's Clifford> dump/load facilities, which would be the highest Clifford> performance. You could dump/load using a Python script and the Clifford> Django ORM. You

Re: Django development workflow

Gour wrote: >> "Clifford" == CLIFFORD ILKAY writes: > Clifford> To keep it simple, we use PostgreSQL in development, QA, and > Clifford> production and on those projects where we're forced to use > Clifford> MySQL due to client requirements, then MySQL everywhere.

Re: Django development workflow

Gour wrote: > When working on the code for e.g. desktop application, I'd put stuff in > e.g. > > $HOME/projects/project_1 directory under DVCS and regularly push to some > 'centralized' server, provide tarballs for releases etc... > > Now, I wonder what to in case of web development with

Django development workflow

Hi! Being new to Django and web development in general I'm curious to learn about some of its 'best practices'. When working on the code for e.g. desktop application, I'd put stuff in e.g. $HOME/projects/project_1 directory under DVCS and regularly push to some 'centralized' server, provide