look for Dockerfile.envy in user repo with name of new environment about envy HOT 5 OPEN

However, it will not clone repos with just a plain Dockerfile as to discourage bad practice.

Does that mean you'd not be up for having a user specific Dockerfile fallback for projects that don't have a Dockerfile{.envy} around? One of my base images is capable of bringing up development environments for many different projects without the need to write project specific Dockerfiles and I'd love to use that with Envy paired with the support for arbitrary github projects.

from envy.

Yeah I think I'll take that back. It can look for a Dockerfile if Dockerfile.envy doesn't exist.

from envy.

Should we try a Dockerfile.dev before building with Dockerfile? I remember seeing people recommend a Dockerfile.dev for development specific images, so the lookup order would be like:

1. Dockerfile.envy
2. Dockerfile.dev
3. Dockerfile

from envy.

The problem with dev or regular Dockerfiles is they're not necessarily made
for dev environments. My Dockerfile.dev are made to run the app in
development, not provide all the tooling needed to do all related tasks....

On Mon, Jul 6, 2015 at 12:51 PM, Fabio Rehm [email protected]
wrote:

Should we try a Dockerfile.dev before building with Dockerfile? I
remember seeing people recommend a Dockerfile.dev for development
specific images, so the lookup order would be like:

1. Dockerfile.envy
2. Dockerfile.dev
3. Dockerfile

—
Reply to this email directly or view it on GitHub
#15 (comment).

Jeff Lindsay
http://progrium.com

from envy.

Gotcha!

from envy.