Deployd: Create RESTful JSON APIs using a GUI interface
deployd.com
deployd.com
/sigh.
Is it because you don't agree that backend development is complex? Or do you feel differently about the front-end being the part that really matters?
Personally, I'm impressed by this. It seems to me a compromise between MeteorJS/FireDB and "traditional" stacks. It also comes with its own environment to organize my code? Something about that is a little appealing. Maybe limiting too, but appealing.
Actually, the example apps don't really do the platform justice. We (at deployd) use it in consulting projects for building big APIs with complex roles and business requirements. The design of deployd is driven more from lessons learned designing those APIs than from our experiments in TODO-lists.
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.
BTW - it is funny how things circle back - we are coming back to a client-server era. Much like the VB6 days :)
Open source was a no-brainer for us. There are some other key concepts that make it a compelling tool, particularly how easily extensible the platform is.
I haven't downloaded it yet, so perhaps I'm missing something. But our thought was that it mimicked the VB6 "Place Code Here" mentality.
An error has occurred: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}
Either way, this looks like an awesome product and I can't wait to learn more.
Shouldn't this be displayed on the homepage somewhere?
However, I do agree that we need to document the stack better for those that want to install from source, or host it themselves.
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]:
10.4.1 400 Bad Request
The request could not be understood by the server due to malformed syntax.
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it.
[2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10...
Edit: Unless you're saying that 403 should be the default code?
The way you have it setup is fine in my opinion. Maybe add some sugar like: `needsAuth()` which would check for a user and would return `cancel("You're not allowed to do that", 403)` given the user does not exist.
I don't think that's necessary though. I like how it is right now.
Great work.
An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
An error has occurred: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}