Re: setup.py for project?

Hello.

What exactly are you trying to achieve?

If you have some part of functionality that is interesting for other people/projects and hence should be shared via pypi, you should extract it as reusable app. Projects, how ever, are not reusable. If you need a fast way to install al project requirements on your new server, you need to use requirements.txt (and pep freeze).

Some people use virtualization (vm images, vagrant, or even docker) to deploy "project" (with all environment including databases, daemons etc) on staing or production machines. 

Environment configuration engines like saltstack/chef/cfengine/puppet are also used.

An excelent book "Continuous delivery" is all about "how do you deploy your code on production with one click". It may be interesting for you.

On Wednesday, April 1, 2015 at 11:48:26 AM UTC+3, guettli wrote:

Using a setup.py for reusable apps makes sense. This way you can
share the code via a pypiserver.

Our projects are very small. They don't have models, only config. With "project" I mean
the small (in our case) git repo which holds settings.py urls.py.

But does a setup.py make sense for the project?

How do you manage your projects (not apps)?

Regards,
   Thomas Güttler


--
Thomas Güttler
http://thomas-guettler.de/

--
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+unsubscribe@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/dce98931-e73d-44d6-8119-b46b6ee76286%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.