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

Document errors #103

Open
3rd-Eden opened this issue Apr 5, 2013 · 2 comments
Open

Document errors #103

3rd-Eden opened this issue Apr 5, 2013 · 2 comments

Comments

@3rd-Eden
Copy link
Member

3rd-Eden commented Apr 5, 2013

We don't have any documentation on how to handle the issues that are sometimes returned during deployments. For example;

Cannot start application with no snapshots

We should tell them that they have only created the application but have no uploaded their application to our servers yet (assuming that people don't know wtf a snapshot is)

There are a buch more of these errors in our nodejitsu api.
@mmalecki
Copy link
Contributor

mmalecki commented Apr 8, 2013

We should probably return understandable errors instead.
I find WhiteHouse/api-standards to be an interesting standard for errors.

@julianduque
Copy link
Contributor

+1

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
3 participants
@3rd-Eden @mmalecki @julianduque