docker-compose.override.yml

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Done.

Done.

Mentioned this in the README.

Mentioned this in the README.

Left a couple comments. Looking good!

Left a couple comments. Looking good!

Does a dev need to do anything to install git LFS?

Does a dev need to do anything to install git LFS?

We should also probably note that demo-data should be set as well.

We should also probably note that demo-data should be set as well.

I think we should add a sentence to explain that running with perf data is different than running without. Perhaps: If you'd like to start a demo system with a lot of data, then run this script in...

I think we should add a sentence to explain that running with perf data is different than running without. Perhaps:

If you'd like to start a demo system with a lot of data, then run this script instead of running step #2 of Quick Setup.

OLMIS-4701 New demo data image and server config to use it
OLMIS-4701 New demo data image and server config to use it
OLMIS-4701 Add startup script for new demo data

For Ref Distro. Need to run demo data before the services, but need to start db so it is available.

  1. … 3 more files in changeset.
OLMIS-4701 Update Ref Distro with demo data image

Update Ref Distro configuration to now have demo data image. However, Ref Distro can still be started without demo data image with just the base YAML file. Production Spring profile is used in override YAML for stock management so that the service does not try to clean and reinitialize the schema, since the demo data image will have already done it.

    • -0
    • +13
    /docker-compose.override.yml