On 1/15/07, Brent W. Woodruff <brent@...> wrote:
> Webware contributors,
> I have spent several weeks trying to break into web programming with
> Python and away from PHP. Of the many web frameworks I tried, webware
> (mod_webkit2) proved to be the easiest to install and start with. I'm
> looking forward to finally getting started on web development with
> Python. For that, I wanted to say 'thank you' and I hope that
> development continues at a healthy pace for webware.
> Since I am relatively new to webapp development, I have a question
> concerning how a webapp should be designed to function in a virtual
> hosting environment. Should there be one webapp servicing all virtual
> hosts, or should each virtual host run their own copy of the webapp? In
> the case of each host running its own copy, does each deployed webapp
> copy run on its own port?
> I may be showing my inexperience here, but will appreciate your thoughts
> and replies.
> Brent W.
When I have multiple sites on one server (let's say N), I typically
have 1 installation of Apache and N installations of Webware. I like
to run each site as a separate process so I can treat them
independently (restart the app server, view the config log, look at
the memory footprint, etc.)
I like to give each site its own Webware so I can upgrade (or not
upgrade) them independently.
Yes, I use a different port for each one. I just make them up: 8001, 7789, etc.
Also, I always use the MakeAppWorkDir.py script and mod_webkit2
module. Check them out.