CoreCluster · Ship

Git deployments

Connect a repository, deploy on push, and roll back to an earlier release in seconds.

Start free for 30 days ← Back to CoreCluster
manage.corefinity.com/managed-clusters
Deployments plinthwick.studio · production
Switch to manual Deploy now

Deployment mode

⎇ Git · main github.com/brindlewyck/plinthwick
Deploy on push
On
Releases kept
5

Rolling back takes seconds.

  • #48
    a91f3c2 Checkout: delivery slots on mobile

    Today 09:48 · Sam Okafor · succeeded in 54 s

    Live
  • #47
    7bd08e1 Bump Laravel to 12.31

    Yesterday 17:12 · Priya Shah · 61 s

    Roll back to this
  • #46
    c04d9aa Add Mailgun webhook

    Failed at Build · release #45 stayed live

    Failed
  • #45
    e8d2f10 Blog: related posts block

    Mon 11:03 · Sam Okafor · 49 s

    Roll back to this
{  How it works  }

Git deployments, step by step

  1. 1

    Switch the site to Git

    Your current files become release 1. Uploads and config move to a shared folder that every release links to.

    manage.corefinity.com/managed-clusters
    The Deployment mode card, with the site’s files before and after switching to Git
  2. 2

    Connect a repository

    Pick the provider, repository and branch. Turn on deploy on push and the panel adds the webhook.

    manage.corefinity.com/managed-clusters
    Connect a repository plinthwick.studio · production
    Provider
    GitHubBrindlewyck Digital
    GitLabConnect GitLab
    BitbucketConnect Bitbucket
    Repository brindlewyck/plinthwick
    Branch main default
    Root directory (optional) repository root
    Deploy on push to mainOff, a push waits for Deploy now.

    The panel adds a webhook to the repository, so a push can start a deploy.

    Cancel Save repository
  3. 3

    Push, and it goes live

    Each push builds a new release beside the live one, then switches over. A failed health check puts the old one back.

    manage.corefinity.com/managed-clusters
    Deployment #49

    main @ 3c81e07 Checkout: saved addresses · pushed by Priya Shah

    Running · Health check View live output
    1. 1Check out3 s
    2. 2Upload6 s
    3. 3Link shared files1 s
    4. 4Platform commands31 s
    5. 5Switch release1 s
    6. 6Health check4 s
    7. 7Clean up
    ==> Install Composer dependencies
Generating optimized autoload files
==> Cache routes
Routes cached successfully.
==> Cache views
Blade templates cached successfully.
==> Switch release
htdocs -> releases/3c81e07
==> Health check
attempt 1 /cf-health 200 · / 200

    Release #48 stays ready If the health check fails, the previous release goes straight back.

  4. 4

    Roll back in seconds

    Pick an earlier release and confirm. The site points at it straight away. Nothing is rebuilt.

    manage.corefinity.com/managed-clusters
    Roll back to #47?

    htdocs will point at release #47 (main @ 7bd08e1 “Bump Laravel to 12.31”) straight away. Nothing is rebuilt and uploads are untouched.

    ! The database is not changed. If #48 added tables or options, check the site after rolling back.

    Cancel Roll back to #47
manage.corefinity.com/managed-clusters
The Deployment mode card, with the site’s files before and after switching to Git
manage.corefinity.com/managed-clusters
Connect a repository plinthwick.studio · production
Provider
GitHubBrindlewyck Digital
GitLabConnect GitLab
BitbucketConnect Bitbucket
Repository brindlewyck/plinthwick
Branch main default
Root directory (optional) repository root
Deploy on push to mainOff, a push waits for Deploy now.

The panel adds a webhook to the repository, so a push can start a deploy.

Cancel Save repository
manage.corefinity.com/managed-clusters
Deployment #49

main @ 3c81e07 Checkout: saved addresses · pushed by Priya Shah

Running · Health check View live output
  1. 1Check out3 s
  2. 2Upload6 s
  3. 3Link shared files1 s
  4. 4Platform commands31 s
  5. 5Switch release1 s
  6. 6Health check4 s
  7. 7Clean up
==> Install Composer dependencies
Generating optimized autoload files
==> Cache routes
Routes cached successfully.
==> Cache views
Blade templates cached successfully.
==> Switch release
htdocs -> releases/3c81e07
==> Health check
attempt 1 /cf-health 200 · / 200

Release #48 stays ready If the health check fails, the previous release goes straight back.

manage.corefinity.com/managed-clusters
Roll back to #47?

htdocs will point at release #47 (main @ 7bd08e1 “Bump Laravel to 12.31”) straight away. Nothing is rebuilt and uploads are untouched.

! The database is not changed. If #48 added tables or options, check the site after rolling back.

Cancel Roll back to #47
{  What you can set  }

Options and limits

Everything here is per site or per environment, from the panel, with every change in the activity log.

Modes
Manual: SFTP and terminal edits are live. Git: deploys from a repository. Switch either way; history stays.
Providers
GitHub, GitLab and Bitbucket. GitLab subgroups work.
Branch and folder
One branch per environment, and an optional root folder when the site sits inside the repository.
When it deploys
On push, switched on or off per environment. Deploy now takes any branch, or a commit by its full hash.
Releases kept
The last 5 successful releases stay on disk, ready to roll back to.
Kept between releases
WordPress uploads and wp-config.php. Laravel storage and .env. Magento 2 media, var folders and env.php.
What runs
Composer install, then the platform’s steps: cache flushes, Laravel caches and a queue restart, Magento 2 setup:upgrade.
When it fails
A failed build never touches the live site. A failed health check puts the previous release back.

Questions about git deployments

No. Sites start in manual mode, where files you change over SFTP or in the terminal are live straight away. Switch to Git when you are ready, and back again if you need to.

No. A rollback points the site at an earlier release in seconds, without rebuilding it. The database stays as it is, so take a snapshot first when a release changes the schema.

The live release keeps serving. A build that fails stops before anything switches. If the new release fails its health check, the previous one goes straight back.

← PreviousEmail sending Next →SSH, SFTP and terminal
Every walkthrough Back to CoreCluster →
Build
Launch
Ship
Protect
{  CoreCluster  }

See git deployments on your own cluster

Tell us how many sites you run and on what. An engineer sizes a cluster with you and shows you the panel on a live one.

By sending this message you agree to our Privacy Policy .