[uWSGI] uwsgi_admin

Yann Malet yann.malet at gmail.com
Fri Jan 22 14:33:22 CET 2010


Yeah there is few things to decide. for me everything live isolated in a
virtualenv. But I understand that for a production server people would
prefer to have a globally installed packaged (apt-get install).

So it seems that both scenario are important and I don't think that it would
be hard to support them once uwsgi python module adhere to the common python
installation standard (setuptools, distutils). In fact I see 2 things that I
don't know yet how to name :

  * the first one is the uwsgi binary (the command line that we use to start
the uwsgi server)
  * uwsgi python module the one used by the django app : "uwsgi_admin"

A first approach would be to make the second one, uwsgi python module,
installable using "pip install". This will let you choose where you can
install it.
Also I have know idea how to do this yet ... I this may be absolutely not a
good idea.   :-p

I would be glad to hear your thought on this.

On Fri, Jan 22, 2010 at 8:46 AM, Roberto De Ioris <roberto at unbit.it> wrote:

> Il giorno gio, 21/01/2010 alle 18.35 -0400, Yann Malet ha scritto:
> > I have started a branch to repackage the uwsgi admin in a way that it
> > is easy to integrate into existing project. PIP and requirements file
> > are becoming the defacto standard in python realm. So the idea would
> > be to just be able to add uwsgi to a requirements  and to get it
> > downloaded and installed into the python path.
> >
> >
> > Here it is where I stand :
> >
> >
> >     mkdir uwsgi-admin
> >     cd uwsgi-admin
> >     virtualenv ve
> >     pip install -E ve -e hg
> > +ssh://hg@bitbucket.org/yml/uwsgi_admin@packaging#egg=uwsgi-admin
> >     pip install -E ve -r ve/src/uwsgi-admin/requirements.pip
> >
> >
> >
> >
> > This should get you almost setup, there is two remaining issue that I
> > am aware of :
> >   * what is the clean and easy way to install uwsgi into the
> > virtualenv
> This is a big (really big) issue. Where the uwsgi binary need to be
> installed ?
> I prefer to have a uwsgi binary for every project (or in every
> virtualenv). Others prefer to have it in the system path (/usr/bin
> or /usr/local/bin).
> With the new --chroot options you need 2 (!!!) binary, one for the
> startup, another for the reloads in the jail/chroot.
> I would like to address this for the next release...
> --
> Roberto De Ioris <roberto at unbit.it>
> Unbit
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.unbit.it/pipermail/uwsgi/attachments/20100122/63e7514a/attachment.htm 

More information about the uWSGI mailing list