System Configuration
These articles cover the Tomcat instance and host that a self-hosted Cascade CMS runs on, rather than anything configured inside the CMS itself. Most involve editing a file on the server and restarting the instance.
Memory and runtime
- Modifying the heap size
- Modifying the thread stack size
- Modifying application ports — including running more than one instance on a host.
- Pointing Cascade CMS at a Java installation
- Configuring the heap dump on out of memory option
- Upgrading Tomcat independently of Cascade CMS
Security and TLS
- SSL/TLS configuration — preparing a keystore and configuring the connector.
- Forcing connections to use SSL/TLS
- Enabling or disabling TLS versions
- Enabling HTTP Strict Transport Security (HSTS)
- Securing session cookies
- Firewall considerations — the inbound and outbound connections to allow.
Infrastructure and logging
- Load balancing — running several instances against one database.
- Using Apache 2.4 to proxy Cascade CMS
- Configuring outbound proxy support for system-generated emails
- Configuring log rotation and compression
- Modifying the database configuration
- Updating the license key