systemd Service Generator
Describe your app and get a .service unit with restart policy, environment, sandboxing and (optionally) a .timer to run it on a schedule, plus the commands to install and check it.
About the systemd Service Generator
The systemd Service Generator builds a .service unit with the command, working directory, user, restart policy, environment variables, dependencies and optional sandboxing options, and can add a matching .timer so the job runs on a schedule like cron. It also prints the exact install and status commands. Every field is validated so no value can add extra directives.
How to use the systemd Service Generator
- Enter the service name and the absolute path of the command to run.
- Set the user, restart policy, environment and, if you want a schedule, the timer.
- Click Generate unit file and follow the install commands.
Frequently asked questions
Why does ProtectSystem=strict break my service?
It makes the whole file system read-only for the service. List the directories it must write to in the writable paths field, which becomes ReadWritePaths.
How do I check the unit before enabling it?
Run systemd-analyze verify myapp.service, then systemctl daemon-reload and systemctl enable --now. For timers, systemd-analyze calendar checks your OnCalendar expression.
Are my data stored when I use the systemd Service Generator?
The text you submit is processed in memory to produce the result and is not saved. Like any web server, Code Converter logs basic visit data (page, IP address and browser) but never the content you paste.
Is the systemd Service Generator free, and can I call it from a script?
It is free and needs no account or signup. The same tool is available as a REST endpoint at POST /api/systemd-generator; see the API documentation for the fields and examples.