systemd-timer

• 
• Deutsche Version dieser Readme

A simple CLI tool for quickly generating systemd .service and .timer units — as a replacement or modern supplement to classic cron jobs.

---

🚀 Features

• Generates .service and .timer files via CLI

• Supports --user timers (for ~/.config/systemd/user/)

• Optional logging (StandardOutput/StandardError)

• Supports:

  • --calendar
  • --exec
  • --after
  • --environment
  • --output
  • --dry-run

• Tested and typed with Deno + Cliffy

---

🛠️ Installation

You can install systemd-timer directly via shell script:

curl -fsSL https://git.0xmax42.io/maxp/systemd-timer/raw/branch/main/scripts/install.sh | sh

The script automatically detects your platform (Linux amd64 or arm64) and installs the appropriate binary to /usr/local/bin, if permitted (possibly using sudo).

Note:

• A working internet connection is required for installation.
• The integrity of the binary is verified using a SHA256 checksum.
• You can manually inspect the script before execution:

curl -fsSL https://git.0xmax42.io/maxp/systemd-timer/raw/branch/main/scripts/install.sh -o install.sh
less install.sh

Additional options and manual installation methods are available under scripts/install.sh.

---

📦 Example

./systemd-timer create \
  --exec "/usr/local/bin/backup.sh" \
  --calendar "Mon..Fri 02:00" \
  --description "Backup Job" \
  --user \
  --logfile "/var/log/backup.log"

This creates:

• ~/.config/systemd/user/backup.service
• ~/.config/systemd/user/backup.timer

Activate afterwards:

systemctl --user daemon-reload
systemctl --user enable --now backup.timer

---

🧪 Running Tests

deno task test

---

🧰 Development

deno task start create --exec "/bin/true" --calendar "daily" --dry-run

---

🔒 Permissions / Flags

The tool requires the following permissions when running or compiling:

• --allow-env (for $HOME)
• --allow-write (to write .service/.timer files)

During development, usually -A (allow all) is used.

---

📝 License

MIT License