Stackroot 0.3.1

Stackroot 0.3.1

Download and run Stackroot-Setup-0.3.1.exe on Windows 10/11 (64-bit). Update over 0.3.0 — sites, databases, and settings are kept.

Site backup

• Backup list refreshes correctly — if you navigated away from a site's Manage page while a backup was running, the new backup now appears in the list as soon as it finishes, even if you're no longer on the page that started it.
• Skip symbolic links — on by default; turn it off to include symlinked folders (e.g. Laravel's storage:link) as real files in the backup. A warning explains that the link itself won't be restored as a link when this is off.
• Custom ignore patterns — exclude paths from the backup using .gitignore-style patterns, with one-click presets for node_modules, .git, and vendor.

Site restore

• Warns before deleting excluded paths — if a backup was made with ignore patterns, restoring files now lists anything on disk that was excluded from that backup and would otherwise be permanently deleted; check any item to keep it in place.
• Fixed warning banners in the Restore and Import dialogs cutting off long text instead of wrapping.

Upgrading from 0.3.0

Your sites, databases, and settings are preserved. No manual steps required.

Stackroot 0.3.0

Stackroot 0.3.0

Download and run Stackroot-Setup-0.3.0.exe on Windows 10/11 (64-bit). Update over 0.2.9 — sites, databases, and settings are kept.

Site backup

Back up any site with a single action — from the secondary action button on the site row or the Backup button on the site Manage page.

• Choose what to include: site files, databases, processes, and scheduled tasks
• Archive site mode — back up then delete the site in one step (files, databases, processes, and tasks are all removed after a successful backup)
• Progress is tracked in the activity tray; the UI stays responsive while large sites compress
• Backup is saved as a .zip file to the configured backups folder (default: {DataRoot}/backups/sites/)
• A "Backup in progress" banner locks site actions while the backup runs to avoid inconsistent state

The Manage page lists all backups found for the current site, sorted by date, with file size and timestamp. Individual backups can be deleted directly from the list.

Site restore

From within the site's Manage page you can roll a site back to any of its own backups. Two entry points, same flow:

• From the backup list — click Restore on any entry; the backup is already tied to this site, no conflict check needed
• Restore from backup — browse to any .zip file; if the backup belongs to a different site, the restore is blocked and you are directed to use Import instead

Before the restore runs, Stackroot shows a delta preview — a per-item diff across site files, databases, processes, and scheduled tasks:

• Restore — item is in the backup but not currently present; will be written back
• Replace — item exists and will be overwritten with the backup version
• Delete — item exists now but is not in the backup; will be removed

Every item can be toggled individually. Uncheck a Delete item to keep it; uncheck a Restore or Replace item to skip it.

After confirming, the site is overwritten in place — files replaced, databases restored, processes and tasks reset to the backup state. nginx is reloaded automatically.

Site import

Import a backup as a new site — from the sites toolbar, pick a .zip file to import.

The dialog shows what the backup contains and checks for conflicts before allowing the import. All conflicts must be resolved manually before the import can proceed:

• Domain conflict — the site's domain already exists; the conflicting site must be removed or renamed first
• Alias conflicts — one or more domain aliases from the backup already exist on another site; they must be removed from that site first
• Database conflicts — one or more database names are already in use; they must be renamed or dropped first

Once all conflicts are cleared, the import creates the new site and restores its files, databases, processes, and scheduled tasks.

Enhanced site deletion

The Remove site dialog now offers fine-grained control over what gets deleted alongside the site entry:

• Also delete site files — removes the site folder on disk
• Also delete databases — drops linked databases from the server
• Also delete processes — removes linked supervisor processes
• Also delete scheduled tasks — removes linked cron tasks

All options default to off; previously only "delete files" was available.

Custom backups directory

Set a custom folder for all backups under General Settings → Backups folder.

• Applies to both site backups and database backups
• Leave empty to use the default path ({DataRoot}/backups)
• Migration: on first launch, existing database backup files in {DataRoot}/backups/ are automatically moved into {DataRoot}/backups/databases/ to match the new layout

Data reliability

• File read retry — settings and registry reads now retry up to 4 times (with 25–75 ms between attempts) when a concurrent write briefly holds an exclusive lock, preventing spurious read errors under parallel I/O

Upgrading from 0.2.9

Your sites, databases, and settings are preserved. On first launch, database backup files are migrated to the new subfolder layout automatically. No manual steps required.