Development Container for Zest

[chrisaxiom]

When working with an API, a fat container is usually not needed for debugging (log inspection will usually suffice). However for the front end, things like webpack -w and/or webpack dev server that are much more useful for development. Thus, the container would need to be fat, with all the tooling inside. We have a fat container for building, but that container is ephemeral. What we would need to do is perhaps add in another setting DEVELOPMENT_CONTAINER= and/or DEVELOPMENT_DOCKER_FILE. A sight issue however, in that it doesn't look like docker nor docker-compose support multiple .dockerignores, so we would have to dump the output of zest build into another folder, and have zest bundle pick up only stuff in that folder.... which is not ideal I suppose.

[AndrewBurian]

Front End

Container

[chrisaxiom]

When I mean "front end" container, it comes with some kind of "front-end backend" built in (lighttpd, node, go, scala, etc). I suppose for static files, they can just be served from a CDN.

[AndrewBurian]

I guess I was going to have to tackle FE file server containers eventually.

[chrisaxiom]

Working with @callmenick to see how this is best done. May not need any additional changes.

[chrisaxiom]

Its looking like docker makes any issues with tooling worse (webpack/sass-node), so this is on hold for now.