From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com> After reading the comments from Zhou Zheng Sheng, I simplified the work I did in version 2 to run only one cherrypy process instead of two processes, one for frontend and another for the backend. Nginx is still being used as a reverse proxy to allow kimchid to run as root, but not being exposed to the outside. As Zhou mentioned, it is to little avail to run frontend and backend separately if the exposed port is running by the reverse proxy anyway. He mentioned the RPC approach as a best long-term approach, which I agree. We can solve this issue right now and the work in a more suitable solution, such as RPC, and then ditch nginx. Daniel Henrique Barboza (3): Github #329: kimchid script changes Github #329: nginx proxy template Github #329: .gitignore, spec and readme changes .gitignore | 1 + contrib/kimchi.spec.fedora.in | 2 + contrib/kimchi.spec.suse.in | 2 + docs/README.md | 4 +- src/kimchid.in | 111 ++++++++++++++++++++++++++++++++++++++---- src/nginx.conf.in | 55 +++++++++++++++++++++ 6 files changed, 164 insertions(+), 11 deletions(-) create mode 100644 src/nginx.conf.in -- 1.8.3.1