Allow release building without starting containers

[BrianSipos]

Currently the ./build.sh tar will fail if it is run on a fresh docker state with no cached non-built images (e.g. redis). Running a ./build.sh before this will cause the images to be downloaded and cached but this behavior is confusing.

This can also be helped by adding build: sections to each appropriate container within the docker-compose.yml so that docker itself knows which images are external and then docker compose ... pull --ignore-buildable will work to cache these images.

[DavidEdell]

Build sections have been added to the *compose.yml files on the dsn-devel branch, see #134 and #141 for details. These changes deprecate usage of the build.sh script in favor of *-compose build.

An export.sh script is provided for convenience to quickly export all built containers into a single tar.gz file for deployment.

[BrianSipos]

@DavidEdell is there any value in keeping the build script? Maybe just move the checking portions into a check.sh and remove the build.sh and remove its references from the docs.

[DavidEdell]

If we've eliminated it's usage from all parts of the deployment (ie: AMMOS production) process, then it would make sense to remove it.

If the check component is the only piece remaining, as you say, that can&should be moved into it's own script. The tar export capabilties have already been migrated into an export.sh script, and import can be handled by standard docker/podman commands.

[mfarina1]

This issue is covered by the merging of the dsn-devel branch PR #178