~the shittiest process manager in the world~
lilp watches git repositories for changes, clones them when they arrive, and then runs arbitrary commands for you after the cloning is complete.
lilp is intended to be used like a service manager that is easy to keep everything up to date with. lilp is especially nice to use with simple scripts, statically compiled binaries, etc. you may also use it as a build service.
all logs for your processes go to /var/log/lilp/service-name/stdout and /var/log/lilp/service-name/stderr.
lilp is stupid, but resilient if your process exits quickly, lilp will start it again immediately fork bombbbbb lilp is asking to be hacked probably dont run lilp as root tbh lilp provides no process isolation lilp runs cron jobs better than cron tho i built lilp because im extremely lazy lilp was made to run binaries and scripts
git clone https://git.j3s.sh/lilp cd lilp && go build mv lilp /usr/sbin/lilp mkdir -p /etc/lilp /var/lib/lilp cp contrib/example-config /etc/lilp/config
cp contrib/lilp.service /etc/systemd/system/lilp.service systemctl daemon-reload && systemctl start lilp
cp contrib/lilp.initd /etc/init.d/lilp service lilp start
clone = the git url to clone & watch. takes the ref argument. ref = the git ref (branch or tag) to clone + watch for changes *run = command to run (order matters) - use this to start your service / job
the config format is very strict. it goes:
process "processname" definition "argument"
process "gitea" clone "https://github.com/go-gitea/gitea.git" ref "v1.16.1"
run "apt -q go || apt install go" run "go build" run "GITEA_PORT=8086 ./gitea"
process "backup" clone "https://git.j3s.sh/backup-stuff" ref "main" run "apt install rsync -y" run "./my-backup-script && sleep 8600"
process "loldockerino" run "docker run redis"
process "loldockerino" run "echo hi mom"
git clone https://git.j3s.sh/git/lilp