search

terranodo / landscapeportal

landscape portal geonode_project
0 stars 1 forks source link

nginx/gunicorn or apache #9

Closed matthewhanson closed 9 years ago

matthewhanson commented 9 years ago

I've been using nginx/gunicorn for the last couple of years now with GeoNode. There is no requirement for the web server. I'm fine with either one, though lean to nginx/gunicorn.

Either way, template config files for the selected web server (and application server in the case of gunicorn) should be included in a geosites_template/config directory.

jj0hns0n commented 9 years ago

+1 on nginx/gunicorn if the setup is documented and scripted. Lets confirm with Erick.

jj0hns0n commented 9 years ago

@eomwandho this is your decision

matthewhanson commented 9 years ago

using nginx and gunicorn

eomwandho commented 9 years ago

We don't mind using either nginx or gunicorn for performance reasons, as long as setup is well documented and we would be able to do some configuration similar to old Apache like proxy pass etc. I'm not familiar with gunicorn so I will lean more towards nginx

matthewhanson commented 9 years ago

gunicorn is the application server and is used with nginx which is the web server.

With apache there is a wsgi module for that, but with nginx you use a separate application server.

nginx configuration is just as easy as apache, no problem setting that up.