Testing cside on staging Environments
Learn how to test cside on staging environments and understand important considerations.
Overview
Our customers often like to test out the edge infrastructure on a staging environment before taking it to production. While this is fully supported, it's important to note that developer environments differ from production sites in several ways.
Common Considerations
IP Restrictions
If a staging environment is only accessible to specific IPs, we cannot retrieve the payload of first-party scripts.
- Third-party scripts will continue to work as they are typically publicly accessible
- The dashboard will still display the list of scripts but won't show the payload of first-party scripts
SSL Certificates
First-party scripts require valid SSL certificate validation.
- Self-signed certificates will prevent first-party scripts from appearing in the dashboard
- Ensure your staging environment uses valid SSL certificates for full functionality
Local Testing
Local testing environments are supported.
Important
For cside to route scripts correctly through Gatekeeper, the host header must match the site's host header configured in cside.
Additional Notes
For more information about staging environments and licensing considerations, see the Caveats page.
How is this doc?