<tt><font size=2>> From: mrunge@matthias-runge.de</font></tt>
<br><tt><font size=2>> To: <devel@lists.fedoraproject.org></font></tt>
<br><tt><font size=2>> Date: 01/21/2014 15:38</font></tt>
<br><tt><font size=2>> Subject: Re: Best Practices for Django App Packaging</font></tt>
<br><tt><font size=2>> Sent by: devel-bounces@lists.fedoraproject.org</font></tt>
<br><tt><font size=2>> <br>
> On 01/21/2014 05:22 PM, John.Florian@dart.biz wrote:<br>
> <br>
> >> [1]<br>
> >> </font></tt><a href="http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/"><tt><font size=2>http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/</font></tt></a><tt><font size=2><br>
> >> openstack-dashboard.conf<br>
> >> [2]<br>
> >> </font></tt><a href="http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/"><tt><font size=2>http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/</font></tt></a><tt><font size=2><br>
> >> openstack-dashboard-httpd-2.4.conf<br>
> >> [3]<br>
> >> </font></tt><a href="http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/"><tt><font size=2>http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/</font></tt></a><tt><font size=2><br>
> >> python-django-horizon.spec<br>
> > <br>
> > Thanks Matthias! That's quite a complicated example, although
I can see<br>
> > there's much I can learn from it. Unfortunately, it's not
the ideal<br>
> > example because it moves everything that setup.py builds into<br>
> > /usr/share/openstack-dashboard. I need to keep stuff under<br>
> > /usr/lib/pythonX.Y/site-packages so that the other, non-Django,
parts<br>
> > continue to work as expected. (I suppose I could just relocate
the<br>
> > Django-parts of the build, but sounds like it will break more
things<br>
> > that it will help.)<br>
> <br>
> Yes, you're right. It's not the ideal and simple example.<br>
> <br>
> On the other side, it doesn't matter if you put all that stuff to<br>
> /usr/share or to %{python_sitelib}<br>
> <br>
> Basically, you just need the two files. Stephen had another, more
simple<br>
> example. This gets the job done. For most real world deployments you'd<br>
> need some more config changes (database, caching, ssl, and more securing).<br>
> <br>
> Matthias<br>
</font></tt>
<br><tt><font size=2>Yup, I'm seeing it now. I realize sqlite is
normally used for production deployments, but in my case I would have been
totally fine with it since I know the number of "user" connections
is always going to be less than 20 or so: one real human on rare occasions
and the rest from machines that are almost always going to get a cached
page since they're each asking once a minute for their own same page. However,
SELinux made me adopt the better practice of using Postgresql since all
the policy is there for that. :-)</font></tt>
<br>
<br><tt><font size=2>I've got a deployed (test) setup roughly working now.
Next step is to clean up the "hard to maintain & it's fragile"
aspects. I will probably wind up doing as openstack-dashboard does
and moving some of the python package/modules out of /usr/lib/pythonX.Y
and into /usr/share/my_app since the rpm spec can do that much smartly.
Then my puppet manifests can refer to things that aren't such moving
targets.</font></tt>
<br>
<br><tt><font size=2>I largely want to avoid a big mess of figuring out
how to migrate the deployed instance to new hosts as Fedora releases come
out. (As a rule, we never upgrade; just reinstall with much help
from puppet. Think of it as a fire drill.) Hopefully I'll get
to keep playing with Django in the future so it all doesn't become foreign
6 months from now.</font></tt>
<br>
<br><tt><font size=2>Thanks to all for the pointers. They've been
a big help.</font></tt>
<br><font size=2 face="sans-serif"><br>
--<br>
John Florian</font>
<br>