We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Gonna wire up a D.O. droplet for this, and it’s asking for a hostname—should I stick with api.sizersoze.org?
The text was updated successfully, but these errors were encountered:
Maybe api1.sizersoze.org? On Apr 28, 2014 7:12 PM, "Mat Marquis" [email protected] wrote:
Gonna wire up a D.O. droplet for this, and it’s asking for a hostname—should I stick with api.sizersoze.org? — Reply to this email directly or view it on GitHubhttps://github.com//issues/47 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/47 .
Sorry, something went wrong.
If versioning is your concern, I guess we should rather use a schema like this: api.sizersoze.org/v1/
Eh, not versioning so much as maybe building in some redundancy at some point.
Redundancy should ideally be handled internally under the same subdomain with a load balancer ;) But I don’t have a strong opinion on that.
yoavweiss
No branches or pull requests
Gonna wire up a D.O. droplet for this, and it’s asking for a hostname—should I stick with api.sizersoze.org?
The text was updated successfully, but these errors were encountered: