renamed service

Deploy the CLI as a systemd service for 24/7 operation. Automatic restarts, system-level logging, and production-ready configuration.

renamed service <command> [options]

The service command manages systemd integration. It handles service file creation, enabling at boot, and provides shortcuts for common operations like viewing logs.

Running as a service gives you automatic restart on crashes, system-level logging via journalctl, and proper resource management.

Subcommands

install

Create and enable the systemd service file.

uninstall

Stop the service and remove the systemd unit file.

start

Start the service.

stop

Stop the service gracefully.

restart

Restart the service.

status

Show service status and health.

logs

View service logs via journalctl. Add --follow for live tailing.

Examples

Install as user service (no sudo required):

$ renamed service install --user

Install with a configuration file:

$ renamed service install --user --config ~/.config/renamed/config.yaml

Check service status:

$ renamed service status

Follow live logs:

$ renamed service logs --follow

Install Options

--user

Install as a user service. Runs without sudo, starts on user login.

--system

Install as a system service. Requires sudo, runs at boot.

--config <path>

Path to YAML configuration file.

--watch-dir <path>

Directory to watch. Can be specified multiple times.

Status Output

● renamed.service - Renamed File Organizer
 Loaded: loaded (/etc/systemd/user/renamed.service)
 Active: active (running) since Mon 2026-01-06 09:15:00
 Main PID: 12847 (node)
 Memory: 48.2M

Tips

Authenticate first — Run renamed auth login before installing the service. The service needs cached credentials to operate.

User vs System — Use --user for personal workstations. Use --system for servers where you want the service to run at boot without user login.

Configuration file — For complex setups with multiple watch directories, use a YAML config file rather than CLI flags.