Most Linux systems uses systemd as init and service manager nowadays.

You can use systemd to start your services, so that they are automatically restarted if they crash, and automatically started when the system boots. You can even do this as a regular user, without root access (then the service will run with permissions of your user), and have it automatically started when the system boots without you having to login.

1. Create the ~/.config/systemd/user directory if necessary:

mkdir -p ~/.config/systemd/user

2. Create a service unit configuration file for your service in that directory ~/.config/systemd/user/myservice.service:

[Unit]
Description=MyService

[Service]
Type=exec
LoadCredential=my-password:%h/myservice.pw
ExecStart=%h/.local/bin/myservice -password-file ${CREDENTIALS_DIRECTORY}/my-password
Restart=on-failure

NoNewPrivileges=true
AppArmorProfile=myservice

[Install]
WantedBy=default.target

3. Load the service definition:

systemctl --user daemon-reload

4. Enable the service:

systemctl --user enable myservice.service

5. Start the service

systemctl --user start myservice.service

6. Enable starting the service on boot without login (you might need to run this as root):

sudo loginctl enable-linger

This will provide the service with credentials from file ~/myservice.pw, and run the service with AppArmor profile myservice (which you must create and load first).

You can publish a Java or Kotlin library built with Gradle on Maven Central like this.

First setup your Gradle build to produce a valid bundle for Maven Central.

1. Include the Maven Publish Plugin in your build.

2. Setup building of Javadoc and Source archives using Dokka.

3. Set the required POM metadata in Gradle like this.

See here for a complete working example.

Now you can run gradle publish to create the Maven bundle in the mavenPublish directory (which you probably want to include in .gitignore).