Your comments

Linux variant is also full of unresolved bugs. This is a real shame!

Well done! This is a kickass approach! And I'm now counting on you also for developing Control on Linux! 🤩

With FIVE YEARS of development we should get top quality coding! 😅😅😅👏

Yes. I'm still running inside Docker with the latest versions, even with the mentioned "dirty method" for applying updates.

My docker-compose.yml looks like this:

version: "3.5"

services:
app:
image: kenayagi/screenconnect
restart: always
command: /etc/init.d/screenconnect debug
#command: sleep 7d # This keeps the service paused while I log into the container and update the service manually. When finished I revert.
volumes:
- ./opt:/opt
ports:
- "8041:8041"
networks:
- traefik_net
environment:
- MONO_MANAGED_WATCHER=true
labels:
- "traefik.enable=true"
- "traefik.http.routers.control.rule=Host(`control.mydomain.com`)"
- "traefik.http.services.control.loadbalancer.server.port=8040"
- "traefik.http.routers.control.tls.certresolver=le"

networks:
traefik_net:
external:
name: traefik_net

(The traefik' part would deserve a separate talk, but that's "optional")

Since the COVID-19 emergency (we are an Italian company) our portal is getting hammered by more hosts than before, and we are having troubles to educate the new operators. We upgraded the license, but that doesn't solve anything.

This missing feature is really a problem now.

Please give us an update on this.

The main problem with my silly setup is that the entire container is backed to a volume.
So docker-style updates won't work.
The right way would be to separate data from executables... And trigger scripts on new image version.