Hacker News Reader

Comment by wereHamster | Hacker News Reader

How does it compare to defining projects in boxen (or puppet)?

This project was meant for upper management, as in a company decides on a project and the developers can instantly get to work. See of it as local development environment. It is also easy to be deleted and removed from the system so that a system stays as clean as possible.

The main vision was that a developer should be set up within minutes and be able to receive updates when an environment changes it's configuration.

I had some more ideas planned, such as work statistics for project management and deployment to production environments.

I can do that with boxen alright: create a project manifest, define where the source is (git repo), what the dependencies are (node version, database server), nginx configuration for the local environment (a foo.dev domain which automatically proxies to the project's web server) etc.

I doubt the upper management can set up these things, they can say that they want to start a new project X, but how exactly the dev environment will look should be, IMO, in the hands of engineers. Lots of technical decisions to be made there.

I do like the UI though.

Many of these decisions would be done through a Beta if I had released it. I did however put a lot of thought into it but after seeing some interesting sign ups from specific companies I decided that a beta would be the way to go.

However, the project was terminated due to the lack of time / financials.

You sure your not just trying to refuge a failed startup and get some good press out of it?

Reply on news.ycombinator.com