Platform · Deploy and updates

Update without fear of breaking what is live.

Repeatable delivery, with a lock, a copy of what will be replaced, a check after the swap and automatic rollback when something fails.

One command, the whole sequence

Project pipeline.

Publishing a project is not copying files. It is compiling resources, synchronising the database and rebuilding the CSS, always in the same order.

Core and project, each in its layer
The core is synchronised first; then the project resources, which may override the core ones.
Database in step with the files
Compiled resources enter the database by natural key, and pending migrations are applied.
CSS rebuilt at the end
Each page's CSS is recalculated from the HTML in the database, so a new page is never served with the old style.

$ c2f project:update-all my-project
> 1/8 syncing core...
> 3/8 syncing resources...
> 5/8 final database validation...
> 6/8 rebuilding derived CSS...
> done

What happens during an update

Safe update, step by step.

Lock

One delivery at a time. A second attempt midway is refused.

Snapshot

What will be overwritten is copied first, along with a database dump.

Swap

Files and database are updated following each layer's manifest.

Check

The installation is tested after the swap.

Automatic rollback

If the check fails, the snapshot files come back on their own.

Implemented and validated on an isolated test tenant, with an artefact broken on purpose to exercise the automatic rollback.

When the server changed on its own

File conflicts, decided one by one.

Every live installation ends up with files that differ from what the delivery brings. The system records the conflict instead of overwriting silently.

Three decisions

Overwrite, keep or merge, file by file, from the panel, the API or the CLI. "Keep" becomes a rule and does not ask again.

Update through the API

One call starts the same updater the CLI uses, answers at once and lets you follow the status, the snapshot and the end of the log.

HTTP API

Recover from the server

The reverse path: bring into the repository what was changed in the running environment, through the same conflict engine.

Go deeper

System updatesPer-layer manifest, conflicts, snapshot and rollback.Update and deploy a projectThe pipeline guide, step by step.Projects and overridesHow a project lives with the core.c2f CLIEvery command, with examples.Releases in CIHow versions are packaged.

See it running on your machine.

Start building Read the docs