The existing SSH logic comes from when we had one container per user, with all services preinstalled. Back then, users could ssh
into the container to manage services, files, and cron jobs. However, in the current setup—where each service runs in its own container—the main container with ssh
no longer makes sense, as it only allows file management, not service control.
I've modified it to ssh
into the host server instead but restricted users to the lazydocker
container. This way, they can execute commands inside any container and monitor them. It gives them more flexibility but might be a learning curve for those used standard ssh and bit docker.
Pushing to testing now—this should be available in next week's update.
