I have a similar development machine set-up, for hosting, I am currently using Rackspace Cloud, as I have full control over deployment options, and it can grow with my apps, scalability is a must. I am currently using Debian Squeeze and editing with the wonderful Kate, and using KIO to edit the odd file on the server via SFTP/Fish. For versioning, I choose Subversion. I also use Subversion for app deployment on the server. On the server, I merely run "svn update" in the app's directory and reload the django instance for the project. It's simple and effective. Subversion also documents my changed and I can easily revert back if something breaks in an update. Although I tend to do a lot of testing before doing an "svn update" on the server. My subversion repo is also located on my Rackspace cloud server.
Question, why do you use VirtualBox? You can make your development Linux box act the same as the production server very easily, as the server is also Linux-based. You can install all the exact same tools as the server, I normally do this. I have MySQL installed on my workstation, nginx, and edit the hosts file to point a beta domain to 127.0.0.1, and configure a virtualhost in nginx. The only difference on my workstation verses the server, is I run django in dev mode and use nginx's "proxy_pass" instead of the options for either fastcgi or wsgi. With different django settings file, you can easily run multiple tests using different configurations. Also, how could Fabric benefit me over a traditional subversion-based deployment? Are there security issues with having a .svn directory in the Python packages? I just read a short tutorial on Fabric, and it does look interesting, it takes away lots of repetitive work. Although running a simple python/shell script over ssh can do the same thing without the extra program: ssh myserver.com python /home/user/ bin/deploy.py $@ I do use ssh pub/private keys for authentication, so creating a local script to run the above command is just as simple as Fabric. Although Fabric probably supports more checks to ensure a stable deployment. Oh and it also helps that my local user matches the user on the target server, it avoids adding the username to the ssh command. I can see how Fabric can scale better than a custom solution though, thanks for that. On Oct 19, 9:02 pm, kenneth gonsalves <law...@thenilgiris.com> wrote: > On Wed, 2011-10-19 at 14:59 +0200, Benedict Verheyen wrote: > > - Debian ( 1st install was potato :)) > > - VirtualBox > > - nginx > > - gunicorn > > - supervisord (watch gunicorn process) > > - git > > - virtualenv > > - pip (coupled with virtualenv, it's a powerful tool) > > - south (easy db migration) > > - fabric (application deployment) > > - Django trunk (for development, I tend to use trunk as it's inhouse > > development) > > - Postgres db with psycopg2 python module > > - memcached > > - workzeug / django-extensions > > - django-registration > > perfect - only celery is missing. > -- > regards > Kenneth Gonsalves -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
