SPA deployment FAQ
What an SPA deployment is, and its Backups, Logs, Power, and Usage tabs.
What SPA deployment is
What is SPA deployment?
A standalone URL for a single-page application, on its own server; it also embeds as a link or an iframe on another site.
Can I deploy more than one SPA?
Yes, each SPA deployment is its own project deployment with its own server, domain, and dashboard page.
Backups
Can I create a backup manually?
Yes, alongside the automatic schedule, from the Backups tab's Create backup action. See Backups.
How many backup copies does auto backup keep?
You choose the number of copies to retain when you turn Auto backups on; manual backups do not count against that limit.
Can I turn Auto backups off later?
Yes, turning it off is its own confirmation step, since it stops future protection rather than deleting anything already saved.
Logs
Do logs help with debugging and auditing?
Yes, each row carries the method called, its status, who called it, their IP, and when, filterable by date range, action, status, channel, and user. See Logs.
Can I export the log?
Yes, Export CSV downloads the current filtered view.
Power
What is the difference between shutting down and destroying a deployment?
Turning it off is a graceful shutdown: the server, its data, and its IP stay allocated, and billing continues. Destroy, in Advanced, is the irreversible one that deletes the deployment. See Advanced.
When should I use Power Cycle instead of turning it off?
When the deployment is unresponsive and you want it back running quickly, a reboot rather than a shutdown and restart.
Usage
What does the Usage tab monitor?
CPU, memory, bandwidth, and disk, each as a live chart over a time range you choose, useful for spotting a bottleneck before it affects visitors.