I just finished the Django app that I want to receive from external user reviews. I would like to run one version and then deploy the private version so that I can enable feedback and add additional features. I plan to do many small iterations of this process. I am new to web development; how do websites usually do this? Is it just a matter of copying my Django project folder to another directory, starting the server there and continuing my dev in the source directory? Or would I like to use a version control system? My intuition is that it is the latter, but if it is, it seems like a huge topic with many uses (for example, collaboration, which is not used here), and I don’t know where to start.
1) Separate URLs www.yoursite.com vs test.yoursite.com. You can also do www.yoursite.com and www.yoursite.com/development etc. You can also create / beta or bet.
2) Keep separate databases, one for production and one for development. Write a script that will copy your database to the dev database. Keep one database for each type of site you create. (You might want to create a beta version or an intermediate database for your tester). Do your own work in the dev database. If you change the structure of the database, save the changes as a .sql file that can be downloaded and run in the site database in real time when these changes are enabled.
3) . -, ( ), . + , / . . , .
4) . . http://ant.apache.org/. , .
5) : cUrl, . . , Ant.
!
: your-site.com test.your-site.com. your-site.com , . trunk test.your-site.com, . .
Jas Panesar , , . , , . , , , .
, - . ( ), - ( mod_python, ). , , HTTP- - (Apache, Nginx, Lighttpd ..). , - , , , , , , . , .
, , , "" -. , .
. - , - . , , . , . - , .
. , , , , . , :
. , , , .
, -? , , . , , :-) , , . "", , - , .
SVN- , , Im done.