Deployd: Create RESTful JSON APIs using a GUI interface

<i>"By removing the complexity of backend development, Deployd lets you focus on the part of your app that really matters: the front-end"</i><p>/sigh.

When I see products like this I always feel like I need a "hacker summary" of them. After some digging around it looks like Deployd is a Node.js/JavaScript application server - you download it and run it, it has a self-contained web server with a default interface, a set of command line tools for managing it and ships with a NoSQL-style data store (in bundles MongoDB). Have I missed anything?

Great Work.<p>suggestion: I would frame it differently - the coolness of what you are doing has nothing to do with the GUI part, but rather, the fact that it is a BaaS (backend as a service) open source. It's a simplified meteor, or an open source parse.<p>BTW - it is funny how things circle back - we are coming back to a client-server era. Much like the VB6 days :)

The title here is wrong, I believe. The APIs produced by this tool are not REST APIs. It doesn't seem possible to be able to satisfy the HATEOAS constraint, and a few other REST conditions are not satisfied. See: <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="nofollow">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hyperte...</a>

GUI Interface. You're kidding right?<p><a href="http://www.youtube.com/watch?v=hkDD03yeLnU" rel="nofollow">http://www.youtube.com/watch?v=hkDD03yeLnU</a>

I would love to look at the docs and tutorials but I keep getting:<p>An error has occurred: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}<p>Either way, this looks like an awesome product and I can't wait to learn more.

I like it. But it would be nice to have the option to deploy on my own server.

This looks pretty interesting.<p>A small thing: For cancelled DELETE requests like shown in the video, it would be better to return 403 Forbidden [1] instead of 400 Bad Request [2]:<p><pre><code> 10.4.1 400 Bad Request The request could not be understood by the server due to malformed syntax. </code></pre> Vs.<p><pre><code> 10.4.4 403 Forbidden The server understood the request, but is refusing to fulfill it. </code></pre> [1] <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4" rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10...</a><p>[2] <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1" rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10...</a>

<i>An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}</i>

This looks like it could be pretty good for prototyping, or maybe a small, low-risk project. It gives the user JS event handlers for server-side events, and there's a simple API for behavior ("protect('model_attr')", "error('the message')"). Not bad.

Are you running your website with deployd? Because it's down :)<p>An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}

Having played around with Parse and StackMob, I agree with fellows HNers that the great importance of Deployd is that it is an open source BaaS. I loved the interface and the custom server side code validation, just like the feature that Parse recently launched. Keep it up!

It looks like their server is melting. Their demo video is here: <a href="http://www.youtube.com/watch?v=I_Jq1BVj6D0&#38;feature=player_embedded" rel="nofollow">http://www.youtube.com/watch?v=I_Jq1BVj6D0&#38;feature=playe...</a>.

I feel like you played techphrase roulette to come up with this idea.

Where's the hypermedia?