On Thu, 2012-03-08 at 16:50 -0800, Theron Luhn wrote:
Each customer is using an identical platform, just with different
database. My thought was to use a single application and, using the
URL to determine the customer, connect to the customer's database. It
would make setup extremely easy to
Hello all.
I'm about to dive into a pretty big Pyramid project. Before I start, I'm
trying to figure out how I'll be running it in production on a VPS or
dedicate server. Should I stick with the Apache that comes preinstalled on
the server and use mod_wsgi, or leave behind Apache entirely
Not talking about Pyramid / WSGI layer itself...
Assuming that these are just skinning a platform for customers, I
would keep away from running each application on a separate IP and try
to handle them via virtualhosts. The rationale for this is:
1. It's easier to step repeat for new clients
2.
Each customer is using an identical platform, just with different database.
My thought was to use a single application and, using the URL to determine
the customer, connect to the customer's database. It would make setup
extremely easy to automate, which is one of the goals for the project, as
I would absolutely recommend nginx for production use.
It does the load balancing pritty well and I had myself asked for advice
on the approach and reverse proxy with paist has given me the best
performance.
Happy hacking.
Krishnakant.
On 09/03/12 00:27, Jonathan Vanasco wrote:
Not talking
