e-mission-docker clean up

[aGuttman]

Remove duplicate files from e-mission-docker repo once the docker changes are added to the server repo

[shankari]

Also, change the examples in the e-mission-docker repo to the new server image.

[shankari]

Also, come up with a mechanism to update the tags in the downstream images automatically.

Concretely, if we push a new release to e-mission-server, the webapp and analysis images and the em-public-dashboard repo need to bump up their numbers and rebuild their own images in a cascading set of rebuilds.

Is this supported by GitHub actions? How does cloud services prefer to deal with it?

[shankari]

Try to merge the differences in the internal emissionlhd repo into the public repo so that we don't have to maintain multiple copies. The changes are not very significant - primarily using jq instead of sed which is not a bad fix to have over the longer term.

[shankari]

Per discussion in e-mission/e-mission-server#875 (comment)
decide whether we want to reintroduce a simple static file or stay with the existing redirect

Clean up this if check
https://github.com/e-mission/e-mission-server/pull/875/files#diff-53eb57ac0b49c269c7061b4c454813b0214d14cfbdd45f6950e9367698891eb4R7
if we decide to stay with the redirect

[shankari]

not sure we need to change bottle live-reload twice
https://github.com/e-mission/e-mission-server/pull/875/files#diff-53eb57ac0b49c269c7061b4c454813b0214d14cfbdd45f6950e9367698891eb4R19
and
https://github.com/e-mission/e-mission-server/pull/875/files#diff-c503cefcceb302a4a81003be47dd394440a744ff027f7e034c2c99ac65ec6996R29

Although I guess it doesn't hurt

[shankari]

Do we need this given that we only call setup_config while building the image now?
https://github.com/e-mission/e-mission-server/pull/875/files#diff-53eb57ac0b49c269c7061b4c454813b0214d14cfbdd45f6950e9367698891eb4R11

[shankari]

Does this need to be fixed?

It doesn't seem to be very worrying as long as the containers that run the actions are wiped after every run.