On 11/22/2010 10:42 PM, Todd Wilson wrote:
I teach a course in which I have students developing unrelated Django
projects on servers of their own choice. As we near the end of the
semester, I would like to set up a single server where I can host all
of these student projects together. I will obviously create a new
user, as well as a new mysql account and database, on this server for
each project, and ask the student teams to upload their project files
into the home directories of these accounts. But what else will I
have to do to make this work?
I suppose I'll have to install the union of all the python libraries
used by the individual projects, but each project will have its own
settings and "local" URL structure, and I'm not sure how all of this
should be coordinated, or what changes I'll have to ask the teams to
make to their own projects to allow this coordination. (The server is
Apache/mod_wsgi.)
Any recommendations?
Probably handiest: provide isolation between the various projects. So
virtualenv or buildout.
What I'd do is to give every student a project skeleton with a pre-made
buildout config including an apache config. Theoretically you should
then only have to run the buildouts and symlink the various apache
configs into your /etc/apache2/sites-available/.
Anyhow, make sure their projects look a bit similar. A setup.py and an
apache config, for instance. Hook it up with virtualenv or buildout.
Reinout
--
Reinout van Rees - [email protected] - http://reinout.vanrees.org
Collega's gezocht!
Django/python vacature in Utrecht: http://tinyurl.com/35v34f9
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
