OVERNODE_ETC Configurations/Secrets distribution optimization.

[jtagcat]

From #19

It also sounds dumb that on the down command, the working dir is reverted aka deleted. Is it really deleted?

Yes, it is because all the persisted state produced in runtime by a container should use a dedicated volume for it (or a database, if it requires synced distributed state).
It is actually not a working directory. It is more like a '/etc' and '/var' on Linux - etc is configs, var is for runtime data. Deleting configs on down is not an issue, because it is only a readonly copy from the current state in the project folder.

By that I meant that let's say we can save bw by for example using rsync (and only transferring the changed parts, if I change a line in 2k line config, that is wasting bw).

Currently it tarzips configs, so you can put quite a bit. Optimisation with rsync would be possible. Would you like to see a dedicated ticket reserved for it now? or wait until someone faces a scalability issue related to slow config upload?