Re: New site: www.portaltotheuniverse.org
Not at all :-) For the site we use: feedparser (nearly obviously for the feed parsing - it's unbeatable) beautifulsoup django-command-extensions django-batchadmin (which I'm very happy to see makes it into Django 1.1) django-mptt (for our menu system) djangodblog PIL threadpool SSLMiddleware For deployment we're using a combination of Paver (with some of our own add-ons), Fabric and virtualenv - all of it works really well together and makes deployment so much easier. Besides that we have a growing common code base for all our sites, that contains all the base components you just need in a site (menus + breadcrumbs generation, a more flexible flatpages app with TinyMCE editor, searching etc). Most of our code base, I'd like to release as open source, but it's quite a big task for the initial stuff we did, which is basically where it gets stuck. The new applications we are doing, we have much greater focus on making them open source, so hopefully you should see small apps coming from us in a not so distant future (ESO is after all funded with tax money ;-). Cheers, Lars On Apr 23, 3:34 pm, Zain Memon wrote: > Cool! Mind sharing the names of any open source django apps you used? > > > > On Thu, Apr 23, 2009 at 6:09 AM, larsholm wrote: > > > Dear all, > > > Allow me to advertise for our new Django based site: > >http://www.portaltotheuniverse.org > > > Keeping up-to-date with cutting-edge astronomy and space science > > breakthroughs has just become that much easier, thanks to the Portal > > To The Universe, the latest Cornerstone project of the International > > Year of Astronomy 2009 (IYA2009). > > > On the tech side it basically boils down to a content-specific feed > > aggregator with a number of important add-ons: > > - human moderation to feature high quality content. > > - embargoed press releases for journalists with login (works in much > > the same way as when journalists can be invited to watch new movies a > > day before everybody else). > > - the RSS crawler is fast and updated very often to keep up-to-date > > with the news development during the day. > > > This is our third major Django-based website we have done here at ESO > > - European Southern Observatory (located in Munich, Germany), and we > > naturally have more websites with astronomy content in the pipeline. > > > Thanks for viewing! > > > Lars Holm Nielsen > > ESO - European Southern Observatory --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
New site: www.portaltotheuniverse.org
Dear all, Allow me to advertise for our new Django based site: http://www.portaltotheuniverse.org Keeping up-to-date with cutting-edge astronomy and space science breakthroughs has just become that much easier, thanks to the Portal To The Universe, the latest Cornerstone project of the International Year of Astronomy 2009 (IYA2009). On the tech side it basically boils down to a content-specific feed aggregator with a number of important add-ons: - human moderation to feature high quality content. - embargoed press releases for journalists with login (works in much the same way as when journalists can be invited to watch new movies a day before everybody else). - the RSS crawler is fast and updated very often to keep up-to-date with the news development during the day. This is our third major Django-based website we have done here at ESO - European Southern Observatory (located in Munich, Germany), and we naturally have more websites with astronomy content in the pipeline. Thanks for viewing! Lars Holm Nielsen ESO - European Southern Observatory --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Weird problem with memcached enabled
Hi What the error says is that it cannot add this together "time.time() + cache_timeout" because on is float and the other is a string, so I suspect that you somewhere have specified *cache_timeout* as a string in quotes instead of just a number (without quotes). Either in the settings.py or in manually in one of the views. Cheers, Lars TheMaTrIx wrote: > Firefox > = All pages OK > > Internet Explorer > = http://www.domain.com gives HTTP500 error with info: > > [error] PythonHandler django.core.handlers.modpython: Traceback (most > recent call last): > [error] PythonHandler django.core.handlers.modpython: File "/usr/lib/ > python2.4/site-packages/mod_python/apache.py", line 299, in > HandlerDispatch\nresult = object(req) > [error] PythonHandler django.core.handlers.modpython: File "/usr/lib/ > python2.4/site-packages/django/core/handlers/modpython.py", line 178, > in handler\nreturn ModPythonHandler()(req) > [error] PythonHandler django.core.handlers.modpython: File "/usr/lib/ > python2.4/site-packages/django/core/handlers/modpython.py", line 155, > in __call__\nresponse = middleware_method(request, response) > [error] PythonHandler django.core.handlers.modpython: File "/usr/lib/ > python2.4/site-packages/django/middleware/cache.py", line 81, in > process_response\npatch_response_headers(response, > self.cache_timeout) > [error] PythonHandler django.core.handlers.modpython: File "/usr/lib/ > python2.4/site-packages/django/utils/cache.py", line 86, in > patch_response_headers\nresponse['Expires'] = > formatdate(time.time() + cache_timeout)[:26] + "GMT" > [error] PythonHandler django.core.handlers.modpython: TypeError: > unsupported operand type(s) for +: 'float' and 'str' > > =http://www.domain.com/?randomstring gives the normal frontpage. > > Any idea whats up here? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Design plus admin question
On top of above approach you can use ideas from
http://code.djangoproject.com/wiki/SplitSettings to separate your
settings into *common* and *deployment specific* settings. In this
way, you won't need to edit the urls file (or have SVN to do it). Just
setup a file on each deployment system specifying special settings,
like db connection or live=true|false. Then just get settings.py to
read the settings from this file.
Cheers,
Lars
On Aug 14, 5:59 pm, "Ritesh Nadhani" <[EMAIL PROTECTED]> wrote:
> Okay.
>
> That was most helpful. I think I will do the same. This is much more
> intuitive.
>
> On 8/14/07, Jon Atkinson <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > I've been experimenting with this too, and I've put a declaration of:
>
> > live = True
>
> > at the top of my urls.py file. Then the sections of my urls.py file
> > which change between development and live are just put inside an if
> > else block. Remember, all the files are interpreted, so this works
> > quite well. An example:
>
> > from django.conf.urls.defaults import *
> > from organisation.views import *
>
> > live = True
>
> > if live:
> > urlpatterns = patterns('',
> > (r'^/mis/?$', 'mis.organisation.views.index'),
> > )
> > else:
> > urlpatterns = patterns('',
> > (r'^/?$', 'mis.organisation.views.index'),
> > )
>
> > I've written post-commit and post-checkout hook scripts for git
> > (though you could do the same easily with SVN) which simple change the
> > live = True to live = False or vice-versa as necessary.
>
> > Hope this helps.
>
> > --Jon
>
> > On 8/14/07, Ritesh Nadhani <[EMAIL PROTECTED]> wrote:
>
> > > Well, I can do that. I just wanted to know if that is the right way. I
> > > have total control over the server as I am the admin. Just wanted to
> > > follow the right way :)
>
> > > On 8/14/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
>
> > > > Why can't you mount it at root on the development and personal
> > > > developer servers so it will match production? Use a different port
> > > > just for Django if you really must because of the personal developer
> > > > servers running other stuff. It is much easier to deal with it being a
> > > > different port number than it being mounted at a different URL.
>
> > > > Graham
>
> > > > On Aug 14, 3:45 pm, acidity <[EMAIL PROTECTED]> wrote:
> > > > > Hi
>
> > > > > This is more of a design question then anything.
>
> > > > > We are using Apache andmod_pythonin our development server. The
> > > > > whole Django project is kept as subfolder in the Apache data
> > > > > directory. So everybody out here can access it over:
>
> > > > >http://192.168.1.10/project
>
> > > > > The project is actually checked out from a subversion code repository.
> > > > > Now every developer checks out the project on his individual machine
> > > > > and works on it.
>
> > > > > A part of the urls.py:
>
> > > > > urlpatterns = patterns('',
> > > > > (r'^project/$', 'project.views.index'),
> > > > > (r'^project/login/$', 'django.contrib.auth.views.login',
> > > > > {'template_name': 'accounts/login.html'}),
> > > > > )
>
> > > > > Now each development server while running their local copy, need to
> > > > > access the project at:
>
> > > > >http://127.0.0.1:8000/projectandit works. Ideally, we would have
> > > > > wanted onlyhttp://127.0.0.1:8000butwe can live with that.
>
> > > > > Now later on when we go live with, the website would be accessed
> > > > > from:http://www.domain.com. Now, during our testing it fails as the
> > > > > regular
> > > > > expression will not match for top level.
>
> > > > > How do you manage such settings? In the end we will just checkout the
> > > > > project in the data directory of Apache and it will go live.
>
> > > > > We dont want to change any settings between test and production so
> > > > > that we dont miss anything or do any unrequired changes.
>
> > > > > Also, it may happen that the DB settings might be different too so
> > > > > what would be the best way to manage such a setting?
>
> > > > > I am sure this is a very common setup.
>
> > > > > Ritesh
>
> > > --
> > > Ritesh
> > >http://www.riteshn.com
>
> --
> Riteshhttp://www.riteshn.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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Installing django on a vm using NAT - SVN 400 bad request
Hi, On Aug 14, 3:36 am, sanchothefat <[EMAIL PROTECTED]> wrote: > Hi, I'm trying to get django going on a debian etch vm I have which > uses NAT to access the web. I found some info that suggested using https:// > but that won't work. Are you trying to get the latest copy of django from the subversion repository? I've been running both debian and ubuntu on my vmware fusion without any problems. Can you connect to anything else outside your computer from your vm? > Should I try ubuntu or is there something in the vm settings I need to > change? I'm still quite new to *nix but making progress so any advice > you can give me on what things to try is very welcome. > > Ta very much, > Rob Cheers, Lars --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
