This is a complete step-by-step guide to get comfortable with docker locally and using it for the dev environment exclusively, which offers a fully sandboxed environment and 1-command environment setup (ie. docker-compose build).
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
MONEY: indicates if one needs a paying subscription to use that project you could just add ($) next to the name ([my project - $] (link to my project) )
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/352
**Author:** [@augnustin](https://github.com/augnustin)
**Created:** 6/13/2017
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (1)
- [`6204f4d`](https://github.com/veggiemonk/awesome-docker/commit/6204f4d752e57e16636e26d0f374137341ba7cb9) New guide to using Docker as a local dev environment
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
<!-- Congrats on creating an Awesome Docker entry! 🎉 -->
<!-- Please fill in the below placeholders -->
http://augustin-riedinger.fr/en/resources/using-docker-as-a-development-environment-part-1/
This is a complete step-by-step guide to get comfortable with docker locally and using it for the dev environment exclusively, which offers a fully sandboxed environment and 1-command environment setup (ie. `docker-compose build`).
# By submitting this pull request I confirm I've read and complied with the below requirements.
**Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.**
- I have read and understood the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- The project submitted is conform to the quality standards outlined in the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md)
- Go to the [contribution guidelines](https://github.com/veggiemonk/awesome-docker/blob/master/CONTRIBUTING.md) and read it again.
RULES (because you probably didn't read the guidelines):
* ORDER: The entries are in lexical order (English letter order)
* CREDIT: Each entry must contains the name of the author with a link to its github account!
* LINK: the link should be to the source code (https://github/account/project) not the website (https://myproject.io <- no!)
* MONEY: indicates if one needs a paying subscription to use that project you could just add ($$$) next to the name ([my project - $$$] (link to my project) )
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/352
Author: @augnustin
Created: 6/13/2017
Status: ❌ Closed
Base:
master← Head:patch-1📝 Commits (1)
6204f4dNew guide to using Docker as a local dev environment📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
http://augustin-riedinger.fr/en/resources/using-docker-as-a-development-environment-part-1/
This is a complete step-by-step guide to get comfortable with docker locally and using it for the dev environment exclusively, which offers a fully sandboxed environment and 1-command environment setup (ie.
docker-compose build).By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
I have read and understood the contribution guidelines
The project submitted is conform to the quality standards outlined in the contribution guidelines
Go to the contribution guidelines and read it again.
RULES (because you probably didn't read the guidelines):
$) next to the name ([my project -$] (link to my project) )🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.