So I was trying to customize my local_settings to include optional stuff in my django app. I was hoping to do it in a way that would make it easy to upgrade between releases since I'm running 1.0 from the deb installer right now. Here are a couple of ways I came across that we might make it easy for people to extend their settings. Specifically I was running into the issue that I need to add Apps and Middleware but I want to keep it separate from the geonode config. Option 1: Easier but doesn't sound like the right way to do it http://www.robgolding.com/blog/2010/05/03/extending-settings-variables-with-local_settings-py-in-django/ Option 2: Sounds like a more robust solution http://djangosnippets.org/snippets/1873/ Wanted to hear what others thought before I filed a ticket (or maybe there's something on the roadmap about this?). Thanks, Alex
The way I am doing it is copying settings.py and urls.py. I get the most flexibility and keeping it up to date with latest developments turns out to be easy. On Jun 16, 2011 10:02 PM, "Alex Mandel" <tech_dev@wildintellect.com> wrote: > So I was trying to customize my local_settings to include optional stuff > in my django app. I was hoping to do it in a way that would make it easy > to upgrade between releases since I'm running 1.0 from the deb installer > right now. > > Here are a couple of ways I came across that we might make it easy for > people to extend their settings. Specifically I was running into the > issue that I need to add Apps and Middleware but I want to keep it > separate from the geonode config. > > Option 1: Easier but doesn't sound like the right way to do it > http://www.robgolding.com/blog/2010/05/03/extending-settings-variables-with-local_settings-py-in-django/ > > > Option 2: Sounds like a more robust solution > http://djangosnippets.org/snippets/1873/ > > Wanted to hear what others thought before I filed a ticket (or maybe > there's something on the roadmap about this?). > > Thanks, > Alex
I think supporting arbitrary extra apps and middleware in the debian package is a pretty lofty goal. I agree with Ariel, it's probably better to just copy settings.py outright. Perhaps a better strategy than making the debian package totally customizable would be to make custom debian packages trivial to build. (So you can easily make a .deb with your geonode customizations, rather than making your customizations on top of the "standard" deb.) -- David Winslow OpenGeo - http://opengeo.org/ On Thu, Jun 16, 2011 at 10:23 PM, Ariel Nunez <ingenieroariel@gmail.com>wrote: > The way I am doing it is copying settings.py and urls.py. > > I get the most flexibility and keeping it up to date with latest > developments turns out to be easy. > On Jun 16, 2011 10:02 PM, "Alex Mandel" <tech_dev@wildintellect.com> > wrote: > > So I was trying to customize my local_settings to include optional stuff > > in my django app. I was hoping to do it in a way that would make it easy > > to upgrade between releases since I'm running 1.0 from the deb installer > > right now. > > > > Here are a couple of ways I came across that we might make it easy for > > people to extend their settings. Specifically I was running into the > > issue that I need to add Apps and Middleware but I want to keep it > > separate from the geonode config. > > > > Option 1: Easier but doesn't sound like the right way to do it > > > http://www.robgolding.com/blog/2010/05/03/extending-settings-variables-with-local_settings-py-in-django/ > > > > > > Option 2: Sounds like a more robust solution > > http://djangosnippets.org/snippets/1873/ > > > > Wanted to hear what others thought before I filed a ticket (or maybe > > there's something on the roadmap about this?). > > > > Thanks, > > Alex >