Django applications in Fedora

[David Malcolm]

Has anyone packaged any Django-based web applications as RPMs for
Fedora?

I noticed that ReviewBoard was being looked at:
https://fedorahosted.org/fedora-infrastructure/ticket/1196

Are any others in Fedora yet?


I'm wondering what the best way of handling configuration (settings.py)
is.

Normally you would set apache config for say "mysite" [1] to:

    SetEnv DJANGO_SETTINGS_MODULE mysite.settings

to get settings from, say, mysite.settings which would
be /usr/lib/python2.5/site-packages/mysite/settings.py

But since this is a config file, should it be below /etc/ ?

Perhaps mysite.settings in an RPM should be a simple python module that
looks in /etc/mysite.conf and gets values from there, and that file
should be %config(noreplace)

Thoughts?
Dave

[1]
http://docs.djangoproject.com/en/dev/topics/settings/#on-the-server-mod-p...

[Ignacio Vazquez-Abrams]

On Wed, 2009-02-25 at 19:13 -0500, David Malcolm wrote:
>  Perhaps mysite.settings in an RPM should be a simple python module
> that
>  looks in /etc/mysite.conf and gets values from there, and that file
>  should be %config(noreplace)
>  
>  Thoughts? 
...

Why didn't I think of that?

Anyways, I'm willing to help you run with this, as I'm trying to package
another Django app (Transifex).

-- 
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;

PLEASE don't CC me; I'm already subscribed

[Michel Salim]

2009/2/25 Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;:
>  On Wed, 2009-02-25 at 19:13 -0500, David Malcolm wrote:
> > Perhaps mysite.settings in an RPM should be a simple python module that
> > looks in /etc/mysite.conf and gets values from there, and that file
> > should be %config(noreplace)
> >
> > Thoughts?
>
>  ...
>
>  Why didn't I think of that?
>
>  Anyways, I'm willing to help you run with this, as I'm trying to package
>  another Django app (Transifex).
>  
The wonderful flexibility of Python. The last time I had a
Python-app-bundling-system-modules, the solution is replacing it with
a stub module that imports the entire system-provided library.

Is there a bugzilla request yet? And is this the same as
Transifex.org? Their website states that it uses TurboGears.

Regards,

-- 
miʃel salim  •  http://hircus.jaiku.com/
IUCS         •  msalim(a)cs.indiana.edu
Fedora       •  salimma(a)fedoraproject.org
MacPorts     •  hircus(a)macports.org

[Ignacio Vazquez-Abrams]

On Fri, 2009-02-27 at 16:57 -0500, Michel Salim wrote:
>  2009/2/25 Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;:
>  > On Wed, 2009-02-25 at 19:13 -0500, David Malcolm wrote:
>  >> Perhaps mysite.settings in an RPM should be a simple python module that
>  >> looks in /etc/mysite.conf and gets values from there, and that file
>  >> should be %config(noreplace)
>  >>
>  >> Thoughts?
>  >
>  > ...
>  >
>  > Why didn't I think of that?
>  >
>  > Anyways, I'm willing to help you run with this, as I'm trying to package
>  > another Django app (Transifex).
>  >
>  The wonderful flexibility of Python. The last time I had a
>  Python-app-bundling-system-modules, the solution is replacing it with
>  a stub module that imports the entire system-provided library. 
A little different this time, but still doable.

>  Is there a bugzilla request yet? And is this the same as
>  Transifex.org? Their website states that it uses TurboGears. 
Nope, I'm still working on the packaging. Yes, it is. 0.3.x is TG, but
0.5 is a rewrite in Django.

-- 
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;

PLEASE don't CC me; I'm already subscribed

[Dimitris Glezos]

On Thu, Feb 26, 2009 at 2:13 AM, David Malcolm <dmalcolm(a)redhat.com&gt; wrote:
>  Has anyone packaged any Django-based web applications as RPMs for
>  Fedora?
>
>  I noticed that ReviewBoard was being looked at:
>  https://fedorahosted.org/fedora-infrastructure/ticket/1196
>
>  Are any others in Fedora yet?
>
>
>  I'm wondering what the best way of handling configuration (settings.py)
>  is.
>
>  Normally you would set apache config for say "mysite" [1] to:
>
>     SetEnv DJANGO_SETTINGS_MODULE mysite.settings
>
>  to get settings from, say, mysite.settings which would
>  be /usr/lib/python2.5/site-packages/mysite/settings.py
>
>  But since this is a config file, should it be below /etc/ ?
>
>  Perhaps mysite.settings in an RPM should be a simple python module that
>  looks in /etc/mysite.conf and gets values from there, and that file
>  should be %config(noreplace) 

Did you happen to have any progress with this?

We're working in packaging Transifex in time for Fedora 11's string
freeze and any input/feedback/reviews would be much appreciated.

  https://bugzilla.redhat.com/show_bug.cgi?id=488151

-d



-- 
Dimitris Glezos
Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B
http://dimitris.glezos.com/

"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--

[Ignacio Vazquez-Abrams]

So, here's what I did:

1) Move settings.py to /etc/%{name}/00-default.conf
2) Process django-settings.py.in (attached), replacing [[confpath]]
with /etc/%{name}, and saving it as settings.py in the project root
3) Profit!

Well, it was a little more complex than that, but that's the gist of it.
Full details here:
http://ivazquez.fedorapeople.org/packages/transifex/transifex.spec

-- 
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;

PLEASE don't CC me; I'm already subscribed

[David Malcolm]

On Fri, 2009-03-06 at 10:51 -0500, Ignacio Vazquez-Abrams wrote:
>  So, here's what I did:
>  
>  1) Move settings.py to /etc/%{name}/00-default.conf
>  2) Process django-settings.py.in (attached), replacing [[confpath]]
>  with /etc/%{name}, and saving it as settings.py in the project root
>  3) Profit! 
Nice.


I guess another way of doing it could have been to add something like
this to the apache config:

   SetEnv DJANGO_SETTINGS_MODULE mysite.settings
   SetEnv DJANGO_SETTINGS_CONFIG_DIR /etc/mysite

and then read that in the mysite/settings.py:
   confpath = os.environ['DJANGO_SETTINGS_CONFIG_DIR']
   conffiles = glob.glob(os.path.join(confpath, '*.conf'))
etc

(I just invented that latter env var)

I note your build seems to do some app-specific extraction of vars from
the tarball's settings.py and then overwrite that with the
post-postprocessed settings.py.in

>  Well, it was a little more complex than that, but that's the gist
> of it.
>  Full details here:
>  http://ivazquez.fedorapeople.org/packages/transifex/transifex.spec 
I notice you also set up SECRETKEY in %post


Are you packaging any apache config files?  I didn't see anything
dropped in /etc/httpd/conf.d   I guess you're separating the deployment
of the app code + data from the wiring of it up to a particular httpd
server.

A related issue is that Django doesn't seem to have a good way to
relocate all URLs in an app below a path.  You can set django.root, but
unfortunately, this breaks all of the internal links.
http://www.djangobook.com/en/beta/chapter21/ notes "The (sic) all your
URL patterns will need to start with "/mysite/". For this reason we
usually recommend deploying Django at the root of your domain or virtual
host."   TurboGears has a url() function for dealing with this, but I
haven't found an equivalent in Django yet.




Hope this is helpful
Dave

[Ignacio Vazquez-Abrams]

On Fri, 2009-03-06 at 12:04 -0500, David Malcolm wrote:
>  I note your build seems to do some app-specific extraction of vars
> from
>  the tarball's settings.py and then overwrite that with the
>  post-postprocessed settings.py.in 
Correct. Transifex has a subpackage, so I needed to perform a little
surgery in order to separate out the settings relevant to that
subpackage.

>  > Well, it was a little more complex than that, but that's the
> gist of it.
>  > Full details here:
>  > http://ivazquez.fedorapeople.org/packages/transifex/transifex.spec
>  
>  I notice you also set up SECRETKEY in %post 
I figured that it was as good a time as any to do it.

>  Are you packaging any apache config files?  I didn't see
> anything
>  dropped in /etc/httpd/conf.d   I guess you're separating the deployment
>  of the app code + data from the wiring of it up to a particular httpd
>  server. 
I left implementation of the HTTP connection to the sysadmin. That way
they can use httpd, lighttpd, flup, or even (ugh) standalone if they
wanted.

>  A related issue is that Django doesn't seem to have a good way
> to
>  relocate all URLs in an app below a path.  You can set django.root, but
>  unfortunately, this breaks all of the internal links.
>  http://www.djangobook.com/en/beta/chapter21/ notes "The (sic) all your
>  URL patterns will need to start with "/mysite/". For this reason we
>  usually recommend deploying Django at the root of your domain or virtual
>  host."   TurboGears has a url() function for dealing with this, but I
>  haven't found an equivalent in Django yet. 
ISTR hearing something about this, but I'm going to need to do some more
research.

-- 
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com&gt;

PLEASE don't CC me; I'm already subscribed