Keep ssh host key unchanged
The server ssh host key should be kept the same no matter what, otherwise the data push get stopped (ssh complaining that the remote host key changed). This happens when docker compose is stopped, for example to force an update of MeteoIO (but if this does have to stop, such as with a problem on the host, the host key would be reset to a random value anyway, thus breaking the data push).
I can think of a few solutions:
- copying the host key into the docker container in order to use the same server key (as this is indeed the same server this could make sense but somehow I'm not so in love with this idea)
- copying a key from a local directory when building the docker image;
- storing the key as well as some other server administration data on a specific volume so once it has been generated the first time, it will be reused even when stopping docker;
- providing the server host key through the admin interface;
Moreover, I think that having to stop docker compose in order to update MeteoIO is not a good solution (at least in the long term) as this interrupts the service. So there should be another way to update MeteoIO. Also picking the latest MeteoIO version from Git is also not that great as when moving toward an operational service, we need better control of the version of MeteoIO that is deployed. Is this something that could be controled through the admin interface or is it a bad idea and should only be set through the command line?
As we get more and more users, this will get critical.