Re: Django deployment practices -- do people use setup.py?

Hello Andrew

i am looking for same actually can u provide me information about that. i think what i understand is here finally the .py code should not go at deployment server and only compile code is going at server and run at deployment server.

so can you provide me the information ?



thanks

On Wed, Apr 25, 2012 at 7:26 PM, Daniel Sokolowski <daniel.sokolowski@klinsight.com> wrote:

Thank you for taking the time to explain; I've reached a similar 'readme' approach here but was hoping for a better solution.

-----Original Message----- From: Andrew Cutler
Sent: Tuesday, April 24, 2012 8:21 AM

To: django-users@googlegroups.com
Subject: Re: Django deployment practices -- do people use setup.py?

On 24 April 2012 02:21, Daniel Sokolowski
<daniel.sokolowski@klinsight.com> wrote:

Both, system libraries and not python files --- anything outside of Python
land that PIP can't handle. How do you handle that if you want a self
contained easy to deploy project?

Well then it's safe to assume that if it's not pure Python, or
directly related to your project then it's out of scope for standard
Python packaging tools.

Python runs just about everywhere, and every platform handles
libraries and app dependencies differently. I don't think that an
elegant, and general cross-platform solution exists. Distutils does
however provide a general method for installing Python (C) extension
modules in a cross platform fashion and there is also a 'data_files'
option for installing non Python files within your virtualenv but this
is as far as it goes.

For Windows you'll need to create an EXE installer or MSI package with
every redistributable that you need (eg Apache/MySQL... oh and
Python). For *nix platforms use the relevant package format eg
RPM/DEB/DMG to install whatever your app depends on, whether it be
MySQL, or some Python module or system library.

The way we've solved it with our Django apps is quite simple. We have
a README file that explains what the general requirements are, and how
to install these requirements for the most popular Linux distros (eg
yum install foo). Our setup.py takes care of everything Python. It's
up to the end user/sysadmin to plumb everything together. Perhaps
later on I'll roll some generic Debs and RPMS that satisfy the
required dependencies, but for now we assume our end users are
technically proficient, so we can get away with a less integrated
approach.

Cheers,

--
Andrew Cutler

--
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.

Daniel Sokolowski
Web Engineer
Danols Web Engineering
http://webdesign.danols.com/

--
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.

--
Pritesh  Modi

 

--
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.