Brewr.io source code released

I didn't know this exsited.

Tools like Vagrant and Docker are great when working on a per-repository basis but I have not found a good solution to install/sync dev environments globally which sounds exactly like what brewr did.

Does anybody know of any simplish solutions to accomplish something like this?

There was bowery.io, they even raised money, they seemingly disappeared [1].

There is also the nix-shell tool from Nix [2] which work great for python, haskell and golang (at least on Linux) but can get very hairy for node and ruby (not only Nix's fault).

I am also working on Pipez [3], which tries to solve a similar problem for frontend development.

[1] http://venturebeat.com/2014/10/21/bowery-io-wants-to-configu...

[2] http://nixos.org/

[3] http://pipez.io/blog/1-tool-hell.html

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.

This is cool, I'm eager to try out and take some ideas.

As a New Year's resolution I tried to improve my dev environment and in January, I created a big yeoman generator for making most of my time consuming tasks trivial, like :

1. Creating a remote repo ;

2. Configuring CI ;

3. Generating project boilerplate files ;

4. etc ...

Doing this with yeoman has it's limits and seems hardly maintainable.