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
Not with geodjango directly, but I'm intersted by the choices you made
regarding the stack.
I'm actually hosting our project on Amazon EC2 (Fedora) and I'm
evaluating scalr.net (Ubuntu) to provide a full redundoncy/scalable
architecture to our project.
We are serving our static from S3, but we
3 matches
Mail list logo
