Show HN: Please review my new Server-Side JavaScript/CoffeeScript servers
cure.willsave.me
cure.willsave.me
> Everything is pre-installed and pre-configured. n* d., nginx already running in front of ExpressJS (site is live when you get the initial build email), mongodb, mongoskin, couchdb, running ExpressJS app, example RailwayJS blog sample already generated, redis installed (for RailwayJS), CoffeeScript installed, VIM support for CoffeeScript installed, psmisc package installed (includes commands like 'killall'), ssh port reassigned, example CoffeeScript code to access MongoDB, example CoffeeScript ExpressJS app, the most popular/recommended NPM/JavaScript packages like Vows, Async, Socket.IO, Backbone.JS, Knockout.JS.
This sentence is difficult to parse. What is n* d? Which technologies belong to what part of your product?
I'd rather have this explained with a bullet list or better yet a nice info graphic.
Primarily the first sentence was a huge turn-off for me. Researching your technology and understanding it is never a waste of time. And Server-Side JavaScript is not some magic bullet where you need to know nothing but can write amazing applications. It is a tricky environment with some great power and massive 'gotchas'.
Personally I think you should either remove reference to research or fully embrace the word. A sales point could be more along the lines of: "Popular server-side JavaScript frameworks already connected and configured to allow you to jump directly into a working example. Great for bootstrapping your research project or spinning up servers for your already written application!" But, I have no silver-tongue so take my wording advice with caution. ;)
Features list needs to give more specifics about RAM, disk space, bandwidth, etc., not just a list of pre-installed software (especially things like Express and Backbone that are trivial for me to bundle with my app when I upload it).
The bullet point about "We don't make you go through a proxy" is useful. You could also brag that WebSockets work—last I checked, this is a big drawback on Heroku.
Is there a reason you refer to Node as "n*d." on the front page, and "nod." on the features page?
Also thanks a lot for checking it out and the feedback. I made the CoffeeScript logo link to your book page.
I also think, although I would have to check, that Linode probably has some kind of N_deJS stackscripts that someone made. Again, I doubt that it is as fully configured or as convenient as my service, and that will cost you almost twice as much, since Linode only has 512MB instances (which for many sites and applications I think is way more than you need with N_de) which cost $19.95/mo. Also that won't give you any kind of DNS setup which I am doing for you just by typing the machine name in (probably not a big deal for a lot of people but it does make it simpler).
Also, I am actually hoping people who know their way around a shell terminal _will_ want this. The idea is to avoid always having to build Node and configure Nginx and reassign ssh and some things that you really don't need/want to do from scratch every time unless you feel like you need to prove you know how or something.
I really appreciate everyone's feedback so far.
I think if no one takes jesus.willsave.me I may set that up myself tomorrow or something. LOL.
Edit: just noticed comments below about licencing of N_de etc etc, so I assume this is the reason