On Wed, Sep 24, 2014 at 4:58 PM, John Schmitt <marmalo...@gmail.com> wrote: > I put my projects in virtualenvs which are in my VMs. It's not like one VM > can only host one project. > > Is that what you mean?
not exactly. if you're using virtualenv, you can directly run the project in your workstation, no need to create any VM for development. save that for the staging step. of course, that's easy almost exclusively for Python projects, in other languages, (but several are getting virtualenv-like features) you might want to isolate and not pollute too much your workstation. in that case, using jails (lxc, docker, even chroot!) makes it easier to 'directly' edit without ssh or 'networked' filesystems. in the worst case (when even the smallest test requires some hardware i don't have), it's easy to add an rsync step to my test script. So i edit locally (with all my version control tools) and for each test all changes are propagated in less time that it takes to restart the process. i guess that what i'm trying to say is that a good editing environment [1] is the most important part of the setup, and it's unreasonable to compromise it just because i don't want the whole messy project requirements in my shiny workstation. [1] i like Kate, which does have remote access to files via ssh without even sshfs, thanks to KDE. but it still adds a split-second lag when i hit save, so i always edit locally, even if i test remotely. -- Javier -- 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 post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoToPSPrbb_CXK-CiN%3D270y0yyVbx748_FAw2%2B%2BMcsxHCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
