4 ms·

Is there a reason it needs to be started as root? In similar self-hosted apps I’ve run into many issues from having scripts run as root. Often the individual ap

Is there a reason it needs to be started as root? In similar self-hosted apps I’ve run into many issues from having scripts run as root. Often the individual apps don’t play nicely enough with each other. Otherwise it looks interesting, I like the UI and the demo instance shows the UX well.

feet 4y ago
My guess would be docker is the reason
- hatware 4y ago
  You don't need to run a script with sudo to use docker. This is targeted at tech-agnostic users, really odd misalignment of goals to ask folks who don't know what they're doing to 'sudo run.sh'.
  - feet 4y ago
    Standard docker installation requires sudo to start containers
    - hatware 4y ago
      You can add your user to the docker group, which does require sudo, but only once.
      - deleted 4y ago
        [deleted]
Terretta 4y ago
Agree, I feel as though it should, itself, be a container, that manages a docker-compose file, then manages the apps using appropriate docker-compose commands. All tested against podman as well. Then the tool could be used readily on the many docker appliances (Synology, Qnap, etc.).