4 ms·
I get the web UI for understanding it, but this is often not how people want to work... What tools are there to allow me to keep my code/API layouts in source
by mpdehaan2 11y ago
I get the web UI for understanding it, but this is often not how people want to work...
What tools are there to allow me to keep my code/API layouts in source control when uploading to this?
I'm sure they exist somewhere, so mostly curious about pointers. (A sample node project using this would probably go a long way)
- BinaryIdiot 11y agoI see this more of a replacement for parse which does a similar thing with cloud code both as far as I can tell there isn't a good place to keep the code / API layouts elsewhere.
- athrun 11y agoThe blog post mentions that you can describe your API using Swagger and then import that. I suppose it means you can keep your Swagger definitions under version control.
- mpdehaan2 11y agothanks!
- pea 11y agoYo! We're building this at https://stackhut.com https://stackhut.com . You can see what an example API looks like @ https://github.com/StackHut/pdf-tools https://github.com/StackHut/pdf-tools . You `stackhut deploy` this and it pushes it to an endpoint you can call over JSON-RPC or HTTP. Would love to hear your feedback (or ping me at leo@stackhut.com if you want me to walk you through anything!)