Are you running your website with deployd? Because it's down :)
An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
Deployd: Create RESTful JSON APIs using a GUI interface
21–30 of 46 posts
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#22It looks like their server is melting. Their demo video is here: http://www.youtube.com/watch?v=I_Jq1BVj6D0&feature=playe....
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#23Great Work. 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 :)
(I work at deployd) Yes, the cycle is funny. We don't usually focus on the GUI when talking about deployd; someone outside the company posted with this headline.
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.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#24Re: Deployd: Create RESTful JSON APIs using a GUI interface
#25Re: Deployd: Create RESTful JSON APIs using a GUI interface
#26"By removing the complexity of backend development, Deployd lets you focus on the part of your app that really matters: the front-end" /sigh.
Why the /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.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#27I like it. But it would be nice to have the option to deploy on my own server.
We made it open source so anyone can run it anywhere. We and others have deployed it to EC2, Heroku, Joyent, Azure, Koding, and I'm sure some others.
When you guys have time do you think you could have install instructions for my own env. Or are the instructions for installing from source at the bottom all I need?
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#28This looks pretty interesting. 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. Vs. 10.4.4 403 Forbidden The server understood the request, but is refusing to fulfill it. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec…
That's actually possible, 400 is just the default code: cancel("You're not allowed to do that", 403); I'm not sure why we didn't show that in the video. Edit: Unless you're saying that 403 should be the default code?
Sounds like 400 is the right code for cancelling a request in general.
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.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#29Earlier quoted context omitted.
You can, it's open source. The environment just needs to support Node and Mongo.
> The environment just needs to support Node and Mongo. Shouldn't this be displayed on the homepage somewhere?
We're working on updated content for the site, and details about the underlying stack and requirements for self-hosting will be more prominent.
Re: Deployd: Create RESTful JSON APIs using a GUI interface
#30Earlier quoted context omitted.
We made it open source so anyone can run it anywhere. We and others have deployed it to EC2, Heroku, Joyent, Azure, Koding, and I'm sure some others.
When you guys have time do you think you could have install instructions for my own env. Or are the instructions for installing from source at the bottom all I need?
If you're on Mac or Windows, it's easiest to use the installer. Otherwise (or if you just want to do it yourself), the "install from source" instructions are enough; you'll need both node.js and MongoDB in your PATH.