Saved Scripts

Saved scripts let you store frequently used shell commands as reusable templates. Instead of typing the same cleanup, backup, or maintenance commands each time, save them once and run them on any server.

Creating a Script

1. Navigate to Saved Scripts in the sidebar
2. Click Create Script
3. Give it a name (e.g., “Docker Cleanup” or “Database Backup”)
4. Write the script content
5. Optionally add a description
6. Click Save

Script names must be unique within your organization.

Example Scripts

Docker image cleanup

docker image prune -af --filter "until=168h"
docker builder prune -f --filter "until=24h"
echo "Cleanup complete. Disk usage:"
df -h /

Database backup

TIMESTAMP=$(date +%Y%m%d_%H%M%S)
pg_dump -U postgres mydb | gzip > /backups/mydb-${TIMESTAMP}.sql.gz
echo "Backup saved: /backups/mydb-${TIMESTAMP}.sql.gz"
ls -lh /backups/ | tail -5

Application log rotation

cd /opt/app
docker compose logs --tail=10000 > /var/log/app/archive-$(date +%Y%m%d).log
docker compose logs --since=1h

Running Scripts

Saved scripts can be executed directly on a server from the command execution interface, or scheduled to run automatically using Scheduled Operations.

Managing Scripts

• Edit: Update the name, content, or description at any time
• Delete: Remove scripts you no longer need

Scripts are scoped to your organization. All members with server access can view and use them.

Next Steps

• Scheduled Operations to run scripts on a schedule
• GitHub Actions to trigger scripts from CI/CD