Skip to content

Split Docker Images #1105

Description

@felixgabler

We should follow a slightly different approach when it comes to docker:

  • our images on DockerHub should contain everything that needs to present on the machine in general (tools, DBs, sbt, ...). They should be agnostic to whether we run develop or production (e.g. no CHOKIDAR_USE_POLLING)
  • we should have separate Dockerfiles in this repo as well which install more things according to the project files (e.g. install yarn dependencies with package.json)

Guides:
https://nickjanetakis.com/blog/docker-tip-75-how-to-avoid-node-modules-in-your-volume-mounts
https://mherman.org/blog/dockerizing-a-vue-app/

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions