Flyway does not need to spin up its own service, as it seems to be creating issues for (or at least complicating) deployment. Instead, we should run flyway from within the tefca-viewer app by modifying the docker-compose file.
Acceptance Criteria:
[x] The Dockerfile and dock-compose files are modified to run flyway at startup from within the tefca-viewer service
[x] Flyway does not spin up its own service
[x] Flyway migrations run successfully upon start up
[x] Flyway-specific files, e.g., DockerFile.flyway, are removed from the codebase
Flyway does not need to spin up its own service, as it seems to be creating issues for (or at least complicating) deployment. Instead, we should run flyway from within the
tefca-viewerapp by modifying the docker-compose file.Acceptance Criteria: