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

Stronging up the API side #47

Open
Wilto opened this issue Apr 28, 2014 · 4 comments
Open

Stronging up the API side #47

Wilto opened this issue Apr 28, 2014 · 4 comments
Assignees

Comments

@Wilto
Copy link
Member

Wilto commented Apr 28, 2014

Gonna wire up a D.O. droplet for this, and it’s asking for a hostname—should I stick with api.sizersoze.org?

@yoavweiss
Copy link
Member

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
.

@anselmh
Copy link
Member

anselmh commented Apr 28, 2014

If versioning is your concern, I guess we should rather use a schema like this: api.sizersoze.org/v1/

@Wilto
Copy link
Member Author

Wilto commented Apr 28, 2014

Eh, not versioning so much as maybe building in some redundancy at some point.

@anselmh
Copy link
Member

anselmh commented Apr 28, 2014

Redundancy should ideally be handled internally under the same subdomain with a load balancer ;) But I don’t have a strong opinion on that.

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

No branches or pull requests

3 participants