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.

Sign up for GitHub

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

Jump to bottom

Serve the content API on a subdomain rather than a high port #101

Open
smashwilson opened this issue Mar 9, 2016 · 0 comments
Open

Serve the content API on a subdomain rather than a high port #101

smashwilson opened this issue Mar 9, 2016 · 0 comments

Comments

@smashwilson
Copy link
Member

Rather than serving the content API on a high port, use a subdomain like content.{{ domain }}. This'll be friendlier to the VPN.

We'll have to transition over gracefully to avoid breaking everyone's builds. This'll be easier once more builds are hosted in Strider.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smashwilson