Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for Nginx configuration with CKAN #877

Closed
nigelbabu opened this issue May 7, 2013 · 7 comments · Fixed by #1315
Closed

Add documentation for Nginx configuration with CKAN #877

nigelbabu opened this issue May 7, 2013 · 7 comments · Fixed by #1315
Assignees
Milestone

Comments

@nigelbabu
Copy link
Contributor

We use Nginx and Apache and this needs to be documented.

@nigelbabu
Copy link
Contributor Author

I'm going to push this to 2.2, to land after the doc reorg has landed.

@seanh
Copy link
Contributor

seanh commented Sep 9, 2013

@nigelbabu Any update on this one?

@nigelbabu
Copy link
Contributor Author

I'll add this to my list for next week.

@nigelbabu
Copy link
Contributor Author

@seanh How do you want me to write this documentation? Should I add it as an alternative or should I ask everyone to use Nginx?

@amercader
Copy link
Member

I think we should only explicitly mention how to use Nginx in the source deploy instructions (which already mention Nginx but don't explain how to use it)

http://docs.ckan.org/en/latest/deployment.html

@nigelbabu
Copy link
Contributor Author

The complication is that in the package we have Nginx reverse proxying Apache.

@amercader
Copy link
Member

I think is fine to recommend the apache-nginx setup for source installs as well if we are using it for the package install. We can change the port in step 5, explain why are we using nginx and add an extra step 6 for the nginx conf file. Or if you prefer add it as an optional step at the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants