Hacker News Reader

Tug primarily differs from fig in two ways:

* Less verbose configuration, tries to assume sensible defaults

* Works with apps that do not yet themselves have a Dockerfile

One of the features I heavily use from fig is controlling the runtime docker parameters in fig.yml, i.e the VOLUME, ENTRYPOINT, EXPOSE, WORKDIR sort of stuff. I see you guys made the decision to maintain the runtime commands in your Dockerfile, requiring a rebuild to change it. Everything except Environment.

I guess my question is, why did you guys choose to do that?

I have not found myself needing to change those things very often once I have created the initial Dockerfile.

If you've got the time I'd love to hear more about your workflow at david@nitrous.io

Reply on news.ycombinator.com