Re: About managing dependencies in a collaborative development team and good practices.

On Wed, Feb 22, 2012 at 9:17 AM, Santiago Basulto
<santiago.basulto@gmail.com> wrote:
> I'm unsing virtualenvs and Pip. Seems great, is really easy that way.
>
> What about deployment? Will it be simple? Or should i care about the
> specific webserver?

on deployment there should be a 'real' webserver (as opposed to the
development server) and probably some wsgi server, database, cache,
queues, whatever your project needs.

besides that 'platform' needs, you also have the webapp itself: your
project and all the python dependencies (django, and extra apps like
South, celery, tagging, etc.) for this, it's (almost) the same as for
development: create a virtualenv, pull from repository, and
pip-install all dependencies.

the main difference is that instead of you running the dev-server, the
infrastructure (including your wsgi server) will execute your app.
exactly how that's done is different for each deployment architecture.

--
Javier

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.