SrvYard
Sign in Start free
solutions / statamic

Statamic as a site type of its own, on the Laravel release layout.

Statamic is a Laravel application, and SrvYard deploys it as one: public/ web root, Composer, a shared .env and storage, the scheduler and queue workers from the Laravel panel. You can deploy a repository, or have SrvYard create a fresh site from a starter kit.

default deploy script, zero downtime (edit freely) 
# runs inside the new release folder
$CREATE_RELEASE()
composer install --no-interaction --prefer-dist \
  --optimize-autoloader --no-dev
# front-end install and build, when package.json exists
php artisan optimize
php artisan storage:link --force
php artisan migrate --force
# only if the command exists in your install
php artisan statamic:stache:warm
$ACTIVATE_RELEASE()
$RESTART_QUEUES()

01What a Statamic site gets

Statamic site type
PieceWhat SrvYard does
Web root /public, with every request that matches no file sent to index.php.
Releases A zero-downtime site builds each deploy in its own folder and switches current when the script succeeds. .env and storage are shared between releases. Chosen when the site is created, not changeable later.
Environment The first .env is built from .env.example, with the app name, URL, application key and, if you connect one, the database. A Normal and a Developer editor; only roles with the environment permission can read or write it.
Stache The default script runs php artisan statamic:stache:warm before the switch when that command exists, so the first visitor does not pay for building the cache.
Scheduler and queues The Laravel card on the site overview applies: the scheduler as one cron job that runs schedule:run every minute, queue workers as Supervisor processes, and the switches for Horizon, Reverb and Inertia SSR when composer.lock has the package.
PHP PHP 8.1 to 8.5 side by side; each site picks one. Composer and npm credentials for private packages are kept per site.
Front-end build npm by default; pnpm, Yarn or Bun if the repository has the lock file. The build runs inside the new release.

02Two ways to start

the New site form

Install a repository

Connect GitHub, GitLab or Bitbucket, or give a Git URL. SrvYard clones the branch, runs your deploy script and from then on every deploy works as on a Laravel site: push to deploy, deploy hook, API, rollback.

Use a starter kit

SrvYard runs composer create-project statamic/statamic on the server, installs the kit with php please starter-kit:install and creates the super user you name (an email and a password of at least eight characters). It keeps the password encrypted only until the site is installed.

The kits on offer are a fixed list of 13: Agentic, Alt Starter Kit, Bedrock, Blogo, Cool Writings, Courses, Doogie Browser, Frontee Boilerplate, Gustamic for Restaurants, HyperCard, Link in the Bio, Multisimplicity and Spin Up Statamic Starter. A kit outside the list is refused.

A starter-kit site has no repository and deploys in place. The form warns that a site created without one cannot get one later.

The Install a Statamic application form on its Use a starter kit tab: server, starter kit, super user email and password, free domain
fig 1The starter kit tab: choose a kit, then name the super user. The other tab takes a repository.

03Where the content lives

a flat-file CMS meets release folders

If your Statamic install keeps content, users or uploaded assets in files, note that on a zero-downtime site each deploy is a fresh clone of your branch, and only .env, storage and the shared paths you add are carried between releases. So a page an editor saves in the control panel on the server, inside a folder that is neither in Git nor shared, is not in the next release.

Decide this before the first deploy. Either keep content in Git and treat the server as read-only for editors, or add the folders your control panel writes to (whichever your install uses) under Shared paths in the site’s deployment settings, or choose to deploy in place when you create the site. SrvYard has no Statamic-specific content sync: how content gets between your machine and the server is up to you.

Shared paths, health checks and release retention, in the docs

04Not covered

so you can rule it out early
  • Docker and Laravel Sail setups: SrvYard does not deploy or manage containers.
  • Octane with zero-downtime releases: it keeps the app in memory and cannot follow the switch.
  • Rolling back database migrations. A rollback repoints the release folder only.

Statamic licence keys are not managed by SrvYard; they belong in the site’s environment like any other setting. The sites run on an Ubuntu server with Nginx and PHP-FPM that you pay your own provider for.

Need a hand deciding? Describe your site.

05Read more

Laravel on SrvYard

The framework flow a Statamic site shares: releases, scheduler, workers, Horizon.
The Laravel panel, in the docs

Every switch on the Laravel card and how to undo it.
Deployments

Releases, rollback, the health check and every way to trigger a deploy.

06Statamic questions

answers from the docs
Is Statamic deployed like Laravel?

Yes. Statamic is a Laravel-based site type: public/ web root, Composer, artisan, a shared .env and storage, and the Laravel panel for the scheduler and queue workers. The default script also warms the Stache when the command exists. See Use the Laravel panel for the scheduler, queues, Octane and maintenance mode.

Which starter kits can SrvYard install?

A fixed list of 13: Agentic, Alt Starter Kit, Bedrock, Blogo, Cool Writings, Courses, Doogie Browser, Frontee Boilerplate, Gustamic for Restaurants, HyperCard, Link in the Bio, Multisimplicity and Spin Up Statamic Starter. A site made from a kit has no repository and deploys in place. See Create a site on your server.

My editors save content in the control panel. Will a deploy overwrite it?

On a zero-downtime site each deploy is a fresh clone, and only .env, storage and the shared paths you add are carried over. Content written outside Git and outside a shared path is not in the next release. Add the folders the control panel writes to as shared paths, keep content in Git, or deploy in place. See Deploy hooks, health checks and release retention.

Can I use Octane with Statamic?

Octane keeps the app in memory and cannot follow a zero-downtime switch, so it needs a site that deploys in place. See Deploy without downtime and roll back to an earlier release.

Does a rollback undo database migrations?

No. A rollback only points the site at an earlier release. Migrations that already ran stay. See Deploy without downtime and roll back to an earlier release.

Put a Statamic site on a server you control.

Free: 1 server, 3 sites, 100 deploys a month. Read the docs first if you prefer.