Here's how I've gone from a brand new slicehost slice to dreamy
geodjango server.
Cribbed heavily from other setup tutorials, this collects a bunch of
disparate information into one place.
Stack includes nginx frontend, cmemcache, apache/modwsgi, and postgres
8.3.
I think generally I'm less interested in scaling per-se with this than
the ability to host multiple django sites on a single server without
running out of RAM / CPU. VPS hosting, essentially.
On Oct 1, 4:24 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> Not with geodjango directly, but
, [EMAIL PROTECTED] wrote:
> On Sep 25, 2008, at 9:23 PM, Prairie Dogg wrote:
>
>
>
> > I'm trying to set up a new server to host several existing django
> > sites. The stack is:
>
> > Ubuntu Hardy Heron
> > Apache 2.2 MPM Worker w/ mod_wsgi (for dynamic content)
Conventional wisdom is that mod_python eats a little more
memory than a correctly configured mod_wsgi.
Here are some nice posts about using mod_wsgi in low memory
environments:
http://groups.google.com/group/modwsgi/browse_thread/thread/d21c334972fc8d37
I'm trying to set up a new server to host several existing django
sites. The stack is:
Ubuntu Hardy Heron
Apache 2.2 MPM Worker w/ mod_wsgi (for dynamic content)
Nginx (for static files)
I'm migrating away from mod_python. The django apps run correctly
under apache mod_wsgi - I've tested this
Sorry about the thread hijack there, I mistakenly thought the
problems were related.
I'm using Python 2.5 on Ubuntu Hardy. It seems to me that the
issue is the project locale directory is in my project folder.
The fact that the locale folder for my project is called
"locale" is causing a name
I ran into this problem as well when I upgraded to the most recent
django trunk. I found out about it because my tests failed the
following error:
from locale import normalize
ImportError: cannot import name normalize
Whoever is writing the patch for ticket #5494 (http://
django project.
>
> I've had one drama where Gutsy crashed: out of memory, unfortunately I
> didn't realise until all log evidence fell off the end of the syslog
> cliff.
>
> Happy optimising
> Rich
>
> On Apr 27, 3:16 pm, Prairie Dogg <[EMAIL PROTECTED]> wrote:
&g
Hey Everybody,
I've been using django for almost a year now and I've been spending
some time recently trying to optimize the slicehost VPS(s) that I use
to run several django sites I've developed. I wanted to share my
findings with the larger group in hopes that my oversights can be
pointed out
Malcolm: Sorry - it's late over here, didn't mean to mis-type your
name.
File this and previous under: damn-life's-work-with-faint-praise
On Apr 26, 11:29 pm, Prairie Dogg <[EMAIL PROTECTED]> wrote:
> Malcom,
>
> Thanks so much for your tremendous effort and success on thi
Malcom,
Thanks so much for your tremendous effort and success on this!
You rock!
On Apr 26, 11:04 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> I merged queryset-refactor into trunk just now. This was changeset
> r7477.
>
> There are still a couple of enhancements to do, but I've decided
I just did this for the first time last night, although I definitely
don't
know how to write good tests, at least I wrote some tests.
First thing you'll wanna check out if you haven't is:
http://www.djangoproject.com/documentation/testing/
But I assume you have, so I'll just get on to the
Just thought I'd add that I went through the exact same thing, spent a
couple hours integrating django-registration only to find django-
profiles later, gotta say that the little google maps locator in
django-profiles is really nifty. I've had to make some modifications
to django-profiles to
I'm doing the vmware situation for my local machine (Mac OS X).
I built a vmware image for my dev environment to mirror my production
environment (apache / mod_python backend with nginx serving the static
content). The only difference between the two machines is that the
dev machine is running
I'm writing a very simple django app for use on a learning project
that I would love to get some informed commentary on. The app
basically helps users mark content objects that they would like to
watch, and sends out email updates to users whenever objects related
to the "watched objects" have
15 matches
Mail list logo
