Installation and Upgrades
These articles cover self-hosted (on-premise) Cascade CMS instances: getting one installed, keeping it upgraded, and moving it when the server changes. None of it applies to Cascade CMS Cloud, where Hannon Hill runs the application, the database, and the upgrades.
Installing and upgrading
The installer you use depends on the platform. All of them follow the same shape: stop the instance, apply the new files, reapply your customizations, and start it again.
- Installation/upgrade (ZIP) — the platform-independent distribution, used on Linux and *nix.
- Installation/upgrade (macOS)
- Installation/upgrade (Windows), plus adding or removing the Windows service
- Running Cascade CMS as a Linux service — systemd and init.d
- Cascade CMS 8 upgrade prep guide — what to clean up before a version 8 upgrade
Database and server
- Database — vendor-specific setup for MySQL, SQL Server, and Oracle, plus backups and size management.
- System configuration — the application server itself: heap and ports, TLS, logging, proxying, and load balancing.
- Configure a web server for publishing — the receiving end of a publish job.
Moving and testing
- Migrating Cascade CMS to a new server
- Setting up a test environment — including how to stop a copy from publishing or emailing.
- Migration Tool — bringing content from an existing site into Cascade CMS.