<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M2B8LK4" height="0" width="0" style="display:none;visibility:hidden">

Introducing a streamlined approach to showcase WebSight CMS using GCP Cloud Run!

Tomasz Michalak
Nov 10 5 min read

WebSight CMS employs proven practices and technologies to ensure ease of customization and maintenance, providing a cost-effective alternative to enterprise-level content management systems like Adobe Experience Manager, Sitecore, or Drupal.

As a product engineering team, one of our primary objectives is to enable customers and partners to learn WebSight CMS and practice building websites using it. To achieve this, we are placing a strong emphasis on simplifying the initial setup and configuration process to drive a wider adoption. We're implementing techniques like containerization and continuous deployments to ensure WebSight CMS is enterprise ready while still keeping the process straightforward in the early stages. As a result, we're seeking more lightweight alternatives to Kubernetes (which we recommend for production environments) for running tests or demoing.

We want our partners to be able to deploy WebSight CMS with ease on their own cloud infrastructure (with Google Cloud Platform as the default choice). The deployment process should be as streamlined as possible. It is the reason we decided to use GCP Cloud Run and Cloud Build. Cloud Run leverages containers as a deployment unit and Cloud Build as a CI/CD service. With these tools, WebSight CMS can offer our partners a straightforward deployment process, allowing a single command deployment to the cloud. No container registry, Kubernetes cluster, or Helm charts are necessary. All that's needed is a Google Cloud Platform account. 

We believe this approach is the most effective way to encourage the adoption of WebSight CMS and introduce DevOps practices without overwhelming engineering teams with too many new concepts and tools. For a step-by-step guide on deploying WebSight CMS on GCP Cloud Run, refer to this guide.

Here are the key takeaways for our demo environments:

  1. Learning and Training: These environments are invaluable for training and learning purposes, offering developers a hands-on experience with WebSight CMS.

  2. Feature Showcase: They are designed for showcasing specific features or functionalities to stakeholders, potential clients, or investors, focusing on demonstrating the software's capabilities without delving into the complexities of production-level stability.

  3. Instant Deployment: Our deployment guide ensures that your WebSight CMS demo instance is up and running in no time. With just a few clicks, you'll have a fully functional GCP Cloud Run CMS instance at your disposal. No intricate configurations or technical expertise required.

  4. Public Accessibility: GCP Cloud Run allows development teams to establish publicly accessible instances with pre-configured DNS and SSL. It enables businesses to access WebSight CMS from anywhere.

  5. Cost Efficiency: We assume that our partners will want to try WebSight CMS as part of their GCP account. Since demo environments are not intended for production use, there's no need for expensive infrastructure or high availability setups.

  6. Content Persistence: It's important to note that GCP Cloud Run is serverless, which means content is not persistent and will be lost during new version upgrades or when the Cloud Run instance restarts.

Demo environments serve as flexible sandboxes for developers, testers, and partners to quickly experiment, evaluate, and demonstrate the capabilities of WebSight CMS. Don't miss out on this transformative opportunity. Elevate your web content management experience with WebSight CMS on GCP Cloud Run today!