You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Team Smurf already uses Docker in day to day development. Building an ENVyfile is an annoying experience for them, because most of their work is transforming the Dockerfile into an ENVyfile - just to have Envy build a docker container.
They suggested that they would like to instead just tell ENVy about their Dockerfile, and move on to defining actions for their project. This allows them to get the best of ENVy's environment management, without re-writing files they've already made.
The text was updated successfully, but these errors were encountered:
Team Smurf already uses Docker in day to day development. Building an ENVyfile is an annoying experience for them, because most of their work is transforming the Dockerfile into an ENVyfile - just to have Envy build a docker container.
They suggested that they would like to instead just tell ENVy about their Dockerfile, and move on to defining actions for their project. This allows them to get the best of ENVy's environment management, without re-writing files they've already made.
The text was updated successfully, but these errors were encountered: