From f6ed9b04deaab32b4ca994907713f171a3bae0a7 Mon Sep 17 00:00:00 2001 From: user333 Date: Mon, 8 Jun 2026 22:10:14 +0000 Subject: [PATCH] add more info --- README.md | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 302fcdf..7d8fe2d 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,23 @@ # servicectl -little service manager thing i made \ No newline at end of file +little service manager thing i made + +# How to set it up + +1. Make a folder to hold all your services. ~/services works well for this. +2. Change every instance of `/home/user/services/` to `/path/to/your/service/folder/` in the script. +3. Add a user for each of your services, and set each user's home folder to `/path/to/your/services/folder//`. +4. Privilege each user with the required privileges for each service. For example, a service to automatically update the system probably needs elevated privileges to use the package manager. +5. su to each service and make a `~/start.sh` and `~/stop.sh` file. In the `start.sh` file, put a shell script to start the service, and in the `stop.sh` file, put a shell script to stop the service. Make sure both scripts are executable. + +# How to use it + +Start a service: + +`# ./servicectl start ` + +Stop a service: + +`# ./servicectl stop ` + +Run servicectl with no arguments to get a list of commands.