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

Serve docs via public/private symlinks, instead of built doc paths. #2191

Merged
merged 47 commits into from
May 10, 2016

Conversation

ericholscher
Copy link
Member

This uses the new [private|public]_symlink roots to serve files from Python.

The goal is to reduce the mass of complexity around the logic we have for serving files in Python, and keep all of that in one simple place in the filesystem around symlinks, both for public & private serving, from nginx or Python.

This changes:

  • Breaks core/urls and core/views into their own directories.
  • Removes support for ssl.$PRODUCTION_DOMAIN -- as this was old and unused.
  • *.dev.readthedocs.io as a local domain for testing subdomains that points at 127.0.0.1 in public DNS
  • Adds SERVE_DOCS as a setting to determine whether to serve public, private docs

@ericholscher ericholscher merged commit a3e5cf3 into master May 10, 2016
@berkerpeksag berkerpeksag deleted the privacy-symlink-serving branch August 18, 2016 03:33
@stsewd stsewd mentioned this pull request Jun 18, 2018
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 this pull request may close these issues.

None yet

1 participant