Split up the compose file and add variations #39
Description
There appears to be include https://docs.docker.com/compose/multiple-compose-files/include/ andextends https://docs.docker.com/compose/multiple-compose-files/extends/ directives in the vocabulary and a way to merge https://docs.docker.com/compose/multiple-compose-files/merge/ compose files when invoking up (or automagically by putting semantics in filenames 🤯 ).
This needs a bit of ivestigation, but my current thinking is we want to use include so that we can have shared compose file fore:
- core data services (mongo, postgres, kafka, tiled, jlab)
- epics serivces (archiver, saverestore, ...)
- set(s) of IOCs
- bluesky / qs / CSS configuration
So that we can have a couple of variations {just ophyd.sim, a bunch of mock caproto IOCs, ADsim + motorsim, beamline-analog, blackhole-IOC, ...} without having to copy-paste a lot of yaml.