These are chat archives for cherrypy/cherrypy

5th
Jan 2017
Jason R. Coombs
@jaraco
Jan 05 2017 01:07
nom nom
Kearney Taaffe
@gitKearney
Jan 05 2017 03:33
is it acceptable to run cherrypy on port 80, or is more acceptable to use NginX and have all requests forwarded to the CherryPy server?
Sviatoslav Sydorenko
@webknjaz
Jan 05 2017 07:54
both are acceptable, it just depends on your case. if it’s a pet/IoT project run it standalone.
if you need some load balancing and/or don’t really need any access validation in CherryPy for your static content, serve your /static directly via nginx and do reverse proxy forwarding from nginx to one or more CherryPy upstreams. you can also add some uWSGI and do uwsgi_pass in nginx instead of making the app bind to the TCP port
Kearney Taaffe
@gitKearney
Jan 05 2017 17:24
I'm wanting to make an API written in cherryPy (no static content)
Jason R. Coombs
@jaraco
Jan 05 2017 17:27
@gitKearney Feel free to let CherryPy bind to port 80. I’ve done that with (small) production websites with success.
Kearney Taaffe
@gitKearney
Jan 05 2017 18:06
Cool. I'm trying to create an simple straight up API using CherryPy. One that just processes requests, and spits out JSON

I'm tired of all the monolith PHP frameworks and fed-up with promises in Node. I've always had a thing for Python. Played around with CherryPy for a job interview with DropBox, and haven't touched it in years.

I got the chance to use whatever language I wanted for a project at work. I chose CherryPy, got to set it up how I want (MCP) and it's been working with an Angular front-end no problem