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

Configurable service URL #1976

Closed
tilgovi opened this Issue Feb 25, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@tilgovi
Copy link
Contributor

tilgovi commented Feb 25, 2015

Since the API is actually a separate application from the site, we should have a way to configure its root URL and use that in path generation throughout the back-end.

This will enable us to use a subdomain for the API.

@nickstenning

This comment has been minimized.

Copy link
Contributor

nickstenning commented Jul 23, 2015

Closing as we're moving away from using the API over HTTP from within the app.

@tilgovi tilgovi reopened this Jul 23, 2015

@tilgovi

This comment has been minimized.

Copy link
Contributor Author

tilgovi commented Jul 23, 2015

This was poorly described above, but it's about configuring the URL we tell the client to use for the API calls. It's easier now than ever, and I've already written it, I just held off because it was orthogonal to the work I was doing in the moment.

@tilgovi

This comment has been minimized.

Copy link
Contributor Author

tilgovi commented Jul 23, 2015

In other words, it's not just about the API client within the server, it's about the browser client: reducing the payload and keeping the session secure by eliminating cookies from API requests, having a separate subdomain for CloudFlare or cache config... etc, keeping this open.

@nickstenning

This comment has been minimized.

Copy link
Contributor

nickstenning commented Feb 10, 2016

This is now done: #2619, #2633, #2878, #2881.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.