We have collection of more than 1 Million open source products ranging from Enterprise product to
small libraries in all platforms. We aggregate information from all open source repositories.
Search and find the best for your needs. Check out projects section.
docker-dev - experimentation with docker as a dev environment
``` $ curl -O https://raw.githubusercontent.com/ericmoritz/docker-dev/master/bin/docker-dev $ chmod +x ./docker-dev```Now that you have the `docker-dev` script, you can start it up``` $ ./docker-dev https://github.com/ericmoritz/docker-dev-home.git```Or you can set `HOME_REPO_URL` in your environment to make ./docker-dev easier to start``` $ export HOME_REPO_URL=https://github.com/ericmoritz/docker-dev-home.git $ ./docker-dev```Config-------`docker-dev` follows the [12 factorconfig](http://12factor.net/config) rule by storing the configurationof your development environment external from `docker-dev`.Simply create a git repo that resembles your ideal home directory andpoint `docker-dev` at it. Bada-bing; bada-boom you have 12-factors!Projects---------`docker-dev` treats your codebases as a [BackingService](http://12factor.net/backing-services) in the 12 Factorparlance. The current working directory is mounted inside thecontainer at `/src` and you are free to alter that directory as yousee fit and those changes will persist the next time you fire up`docker-dev` in that directory.Keep in mind, you should treat the `docker-dev` container hastemporary and commit any changes you make to version control beforestopping the container. The `/src` volume ensures you won't lose yourchanges if the container stops but doesn't ensure that your changeswill exist if the Docker host dies (Backup!).If your `PWD` has a file called `.project_profile` this file will beexecute to configure your container for your porject when you start up `docker-dev`.