What is the best way to deploy a CherryPy application?

[vthakr]

I'm basically looking for the best way to deploy a CherryPy
application. In the past I've used a few frameworks such as Django and
Pylons on the Python side and Rails and Sinatra on the Ruby side. In
all cases, the frameworks have come with a non-production ready server
for development purposes, but for production it was always suggested
that you use something like Apache with either mod_python/mod_wsgi, in
the case of Python, or mod_ruby/mod_rails/mod_rack (i.e., Phusion
Passenger) in the case of the Ruby frameworks. So, my question is,
given that CherryPy comes with a production ready application server,
what is the best way to deploy a CherryPy app, using the supplied
server, or using something such as mod_wsgi with Apache? If it's the
former, then do you also use the CherryPy server to serve static files
as well or is that the job of a dedicated web server such as Apache?
If you use CherryPy behind a web server, is it via mod_proxy or
mod_rewrite to send the requests to the CherryPy server?

Thanks for any help that you all can provide, i really appreciate the
help.

Christopher

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users@...
To unsubscribe from this group, send email to cherrypy-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---

IMHO in any case you should not use CherryPy built-in server for
serving static files. Try CherryPy behind nginx instead of this.
As for me the bunch of CherryPy behind apache/mod_wsgi and nginx works
great.

On Sep 15, 2:07 pm, vthakr <vth...@...> wrote:

> I'm basically looking for the best way to deploy a CherryPy
> application. In the past I've used a few frameworks such as Django and
> Pylons on the Python side and Rails and Sinatra on the Ruby side. In
> all cases, the frameworks have come with a non-production ready server
> for development purposes, but for production it was always suggested
> that you use something like Apache with either mod_python/mod_wsgi, in
> the case of Python, or mod_ruby/mod_rails/mod_rack (i.e., Phusion
> Passenger) in the case of the Ruby frameworks. So, my question is,
> given that CherryPy comes with a production ready application server,
> what is the best way to deploy a CherryPy app, using the supplied
> server, or using something such as mod_wsgi with Apache? If it's the
> former, then do you also use the CherryPy server to serve static files
> as well or is that the job of a dedicated web server such as Apache?
> If you use CherryPy behind a web server, is it via mod_proxy or
> mod_rewrite to send the requests to the CherryPy server?
>
> Thanks for any help that you all can provide, i really appreciate the
> help.
>
> Christopher

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users@...
To unsubscribe from this group, send email to cherrypy-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[vthakr]

Hi Urlin,

Thanks for your answer, and I definitely agree with you that it does
seem a good idea to leave the static file serving to those
applications that were made specifically for that purpose. However,
I'm a bit curious at what brought you to your current setup. You
mention using both Apache and Nginx, so I am assuming that you are
using Nginx as your static file server and Apache/mod_wsgi as your
application server. Am I assuming correctly, that this is your setup?
If so, why did you decide to use Apache as your application server
rather than the one supplied with CherryPy? I know the setup you
described is becoming more and more popular amongst Django users, so
it may be that your answer is every bit as simple as "that's what I'm
used to", which is perfectly fine, but I thought I'd ask just in case
there were any other underlying reasons that you decided not to use
the bundled app server.

Thanks again for your reply, and I'm looking forward to any more
information you can share with me.

Christopher

On Tue, Sep 15, 2009 at 5:29 AM, urlin <eternalurlin@...> wrote:

>
> IMHO in any case you should not use CherryPy built-in server for
> serving static files. Try CherryPy behind nginx instead of this.
> As for me the bunch of CherryPy behind apache/mod_wsgi and nginx works
> great.
>
> On Sep 15, 2:07 pm, vthakr <vth...@...> wrote:
>> I'm basically looking for the best way to deploy a CherryPy
>> application. In the past I've used a few frameworks such as Django and
>> Pylons on the Python side and Rails and Sinatra on the Ruby side. In
>> all cases, the frameworks have come with a non-production ready server
>> for development purposes, but for production it was always suggested
>> that you use something like Apache with either mod_python/mod_wsgi, in
>> the case of Python, or mod_ruby/mod_rails/mod_rack (i.e., Phusion
>> Passenger) in the case of the Ruby frameworks. So, my question is,
>> given that CherryPy comes with a production ready application server,
>> what is the best way to deploy a CherryPy app, using the supplied
>> server, or using something such as mod_wsgi with Apache? If it's the
>> former, then do you also use the CherryPy server to serve static files
>> as well or is that the job of a dedicated web server such as Apache?
>> If you use CherryPy behind a web server, is it via mod_proxy or
>> mod_rewrite to send the requests to the CherryPy server?
>>
>> Thanks for any help that you all can provide, i really appreciate the
>> help.
>>
>> Christopher
>
> >
>

--
Christopher Roach
http://christopherroach.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users@...
To unsubscribe from this group, send email to cherrypy-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[René Dudfield]

I use cherrypy behind apache proxy server - running the cherrypy app
server on linux.  Just because I have other apache sites on there.

I run the servers in screen sessions, started with crontab with
@reboot in case the server is rebooted for some reason.  This makes it
easy for me to update code, and stuff on the servers.

However, cherrypy has been fine for serving static files for me... but
I haven't used it on mega popular websites.

I also use cherrypy in desktop applications.  So I can connect with a
web interface to the desktop applications (and my desktop applications
can talk to each other... even if on different machines).


On Sep 15, 5:07 pm, Christopher Roach <vth...@...> wrote:

> Hi Urlin,
>
> Thanks for your answer, and I definitely agree with you that it does
> seem a good idea to leave the static file serving to those
> applications that were made specifically for that purpose. However,
> I'm a bit curious at what brought you to your current setup. You
> mention using both Apache and Nginx, so I am assuming that you are
> using Nginx as your static file server and Apache/mod_wsgi as your
> application server. Am I assuming correctly, that this is your setup?
> If so, why did you decide to use Apache as your application server
> rather than the one supplied with CherryPy? I know the setup you
> described is becoming more and more popular amongst Django users, so
> it may be that your answer is every bit as simple as "that's what I'm
> used to", which is perfectly fine, but I thought I'd ask just in case
> there were any other underlying reasons that you decided not to use
> the bundled app server.
>
> Thanks again for your reply, and I'm looking forward to any more
> information you can share with me.
>
> Christopher
>
>
>
> On Tue, Sep 15, 2009 at 5:29 AM, urlin <eternalur...@...> wrote:
>
> > IMHO in any case you should not use CherryPy built-in server for
> > serving static files. Try CherryPy behind nginx instead of this.
> > As for me the bunch of CherryPy behind apache/mod_wsgi and nginx works
> > great.
>
> > On Sep 15, 2:07 pm, vthakr <vth...@...> wrote:
> >> I'm basically looking for the best way to deploy a CherryPy
> >> application. In the past I've used a few frameworks such as Django and
> >> Pylons on the Python side and Rails and Sinatra on the Ruby side. In
> >> all cases, the frameworks have come with a non-production ready server
> >> for development purposes, but for production it was always suggested
> >> that you use something like Apache with either mod_python/mod_wsgi, in
> >> the case of Python, or mod_ruby/mod_rails/mod_rack (i.e., Phusion
> >> Passenger) in the case of the Ruby frameworks. So, my question is,
> >> given that CherryPy comes with a production ready application server,
> >> what is the best way to deploy a CherryPy app, using the supplied
> >> server, or using something such as mod_wsgi with Apache? If it's the
> >> former, then do you also use the CherryPy server to serve static files
> >> as well or is that the job of a dedicated web server such as Apache?
> >> If you use CherryPy behind a web server, is it via mod_proxy or
> >> mod_rewrite to send the requests to the CherryPy server?
>
> >> Thanks for any help that you all can provide, i really appreciate the
> >> help.
>
> >> Christopher
>
> --
> Christopher Roachhttp://christopherroach.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To post to this group, send email to cherrypy-users@...
To unsubscribe from this group, send email to cherrypy-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/cherrypy-users?hl=en
-~----------~----~----~----~------~----~------~--~---