Using SubakoOS

SubakoOS presents modules according to each user's grants. Administrators can see and configure the whole instance; other Linux users begin with no module access until an administrator grants it.

Start with the dashboard

The dashboard provides live host health, system identity, resource graphs, and top processes. Use it to confirm that the backend can inspect the host before configuring storage, networking, or automation.

Add users safely

Users authenticate through Linux PAM. An administrator can enroll an existing Linux user or create one, then grant only the modules that person needs. Wheel membership and SubakoOS administrator status are separate controls.

Manage storage

Inspect device identity and filesystem state before mounting. Prefer UUID-backed automount entries for persistent local disks. For remote shares, store credentials through the encrypted secrets path rather than embedding them in mount options.

A mount, firewall, package, or power operation changes the real host. Read the preview and confirmation screens carefully.

Deploy containers

Use the Marketplace or Images view to select an image and tag. Configure container name, ports, volumes, environment variables, and restart policy before deployment. The backend uses rootless Podman and can pull missing images as part of the deploy operation.

Automate maintenance

Scheduled tasks become systemd timers. Use built-in templates for common maintenance, or create a constrained custom task when custom scheduler commands are enabled. Run a new task manually once and inspect its journal before enabling its timer.

Back up before changing

Create named rsync or Borg profiles, choose explicit source and destination paths, and set retention. A successful backup is not the end of the job: test archive browsing and restore a representative file.

Notifications

Configure in-app alerts first, then add SMTP or webhook delivery. Per-event cooldowns prevent repeated host conditions from flooding external channels.

Updates

Host updates use dnf on Fedora and pacman on Arch. Release upgrades use the signed SubakoOS installer flow. Treat container image updates separately: a newer image still needs application-specific release-note and migration review.

Service commands

journalctl -u subakoos -f
sudo systemctl restart subakoos
sudo systemctl stop subakoos

For failure modes and diagnostic steps, continue to Troubleshooting.