Change safely with staging, versions and logs

Change things without your visitors noticing: test on staging first, you can always go back to an earlier version, and the logs tell you what goes wrong.

Staging: test first

Staging is a second environment of your project, next to production. It has its own address, its own variables and its own database, counts towards your plan at no extra cost and is never shown in Google. Staging is in Standard and up, not in Static.

1. Open your project and click production at the top.
2. Click Add staging.

Staging starts as a copy of production. The same button at the top switches between production and staging. When you are looking at staging, it says so at the top.

• Copy production to staging: puts production’s versions and data on staging again. What was in staging’s database is replaced.
• Promote staging to production: exactly the same build goes to production. Nothing is rebuilt. Production’s database and files stay as they are.

Done with staging? Click Remove staging in Project settings.

Go back to an earlier version

Every time your site goes live, Cubli keeps that version.

1. In your project, click Versions. In the advanced view, that is your site’s Deploys tab.
2. Next to an earlier version, click Make this version live.

Nothing is rebuilt, so it is quick. Each version shows when and how it went live, for example via GitHub, the CLI or your AI tool, and Build log shows how it was built.

If a new version fails, the previous one stays online. Your visitors notice nothing.

Read the logs

Click Logs in your project, or your site’s Logs tab. You see the latest lines your site reports, live from the running version. Useful when a page shows an error. For WordPress, switch on Errors to Logs to see PHP errors here instead of on your site.

What happened in your project, by whom and when, is under Activity at the top right.

Need help?

Stuck? Mail support@cubli.io with your project’s name.