This little command line tool helps to speed up common tasks around Craft CMS deployment on fortrabbit. Craft Copy syncs your local development environment with your fortrabbit App — up and down. It conveniently deploys code changes and synchronizes latest images and database entries. This Craft CMS plugin will be installed locally and on the fortrabbit App.
Here is a video introdcution (1.5 minutes).
- A local development environment including: Craft 5 (since version 3), PHP 8 and Composer.
- The following binaries should be executable:
php,mysqldump,gitandrsync - A SSH key installed should with your fortrabbit Account (no password auth so far)
- You need to have an App with fortrabbit
Craft Copy works for Universal Apps and Professional Apps. Asset synchronisation is only available for Universal Apps with local asset volumes. It's known to work locally with Laravel Herd, Laravel Valet and DDEV.
Best install Craft Copy in the terminal on your local computer with Composer like so:
# Jump into your local Craft CMS folder
cd your/craft-project
# Require Craft Copy via Composer
composer config platform --unset
composer require fortrabbit/craft-copy -W
# With the latest version of composer (2.2 or higher) you may see this prompt:
# Do you trust "fortrabbit/craft-auto-migrate" to execute code and wish to enable it now? (writes "allow-plugins" to composer.json) [y,n,d,?]
#
# Confirm with `y`
# Install and enable the plugin with Craft CMS
php craft plugin/install copyYou will be guided through a form to connect your local App with the App on fortrabbit. Craft Copy is available in the Craft CMS plugin store.
Craft Copy will always be executed on your local computer in your local development environment.
The optional {stage} parameter defines which fortrabbit App the command applies to. It is useful when working with multiple fortrabbit Apps as stages. The default parameter is the app name. See multi-staging section below for more.
Some commands are interactive, meaning that you will need to confirm certain potential dangerous operations. You can disable such manual interactions by adding the --interactive=0 flag in most cases. The short alias version is -i=0.
# Connect your development environment with your fortrabbit App
php craft copy/setup# See a list of available commands
php craft help copy# Dump local DB (backup fortrabbit db) and import it to the fortrabbit App
php craft copy/db/up {stage}
# Dump local DB and import it to the fortrabbit App (useful if the fortrabbit db is broken)
php craft copy/db/up {stage} --force
# Dump fortrabbit DB and import it locally
php craft copy/db/down {stage}While you can use git push as well to deploy code by Git to your fortrabbit App, the Craft Copy code commands offer some additional extras: It will check for uncommitted changes and initialize the Git repo if required.
# Push code changes to the fortrabbit App
php craft copy/code/up {stage}
# Pull code changes from your fortrabbit App
php craft copy/code/down {stage}- To prevent a prompt, for instance when running the command in a CI pipeline, you can use
php craft copy/code/up -i=0 -m="your commit message".
Assets in Craft CMS are media files that are uploaded by editors and managed by the CMS. Assets are getting stored in volumes and are not part of Git.
# Sync up a local volume to fortrabbit App
php craft copy/volumes/up {stage} {?volumeHandle}
# Sync down a vlume from the fortrabbit App to local
php craft copy/volumes/down {stage} {?volumeHandle}- The "File System Path" for the Volume setting within the Craft CMS control panel should not be a relative path. You can use the
@webrootalias. - Remote volumes (S3, Object Storage …) are not supported so far
- {volumeHandle} is the handle name of your asset volume in Craft CMS
- To sync all volumes, don't provide a volumeHandle (and add
-i=0to avoid questions) - To test what will actually be synced you can add the
-noption to trigger a dry-run
Often you want to get all the latest content from the App or maybe even push all local changes up to the App. You can use the all command for that:
# Sync database, volumes and git from local to your fortrabbit App
php craft copy/all/up
# Sync database, volumes and git from your fortrabbit App to local
php craft copy/all/down- This is not including the folder action by default.
Craft Copy supports DDEV. Once you got the container running:
ddev auth ssh- Copy SSH keys from the host into the containerddev ssh- Login to the container- From their proceed as required
See our slighlty old blog post on how to set it up together.
This feature will be removed with the next major version since Craft Nitro is retired.
Don't stop. Read on to fully understand Craft Copy!
The setup command creates a configuration file within the Craft /config folder. The file name pattern is fortrabbit.{stage}.yml, where {stage} is how you have defined the fortrabbit App environment in the setup. The default for {stage} is the App name, commonly this can also be production. The file is version controlled and can be shared with the team and includes all basic settings, plus some extras, like before/after commands. When using multi-staging a configuration file will be created for each fortrabbit App. Also see the example file.
Craft Copy incorporates another package called Craft auto migrate. It makes sure that database migrations will always run when deploying to the fortrabbit App. That means that every time you'll push code via Git, a database migration will be triggered and changes from project.yaml will be applied right away, without the need to click the apply changes button with the Control Panel.
The other way around, when pulling down changes, a database migration will also run. This is configured via a default after command in the config file.
Craft Copy alters the behaviour of the ProjectConfig class to prevent Project Config actions in the CP.
By default, we apply the potential changes during deployment after composer install.
At fortrabbit you can set up multiple Apps to create multiple environments for your project. See the multi-staging help article.
Once your Apps are in place, you connect your local environment with each App.
# Run this command to setup a new deployment configuration for each stage
php craft copy/setupThe setup command creates a config file for each App.
# Copy code and db down from 'production'
php craft copy/code/down production
php craft copy/db/down production
# Make changes
# ...
# Copy code and db up to 'staging'
php craft copy/code/up staging
php craft copy/db/up stagingYou can run any script before or after you run common up/down commands with Craft Copy.
- Place the before/after scripts in your Craft Copy config file.
- The before/after commands will run on your local machine, not on the fortrabbit App. To run scripts while deploying, consider the Composer
post-install-cmd.
- code/up
- code/down
- db/up
- db/down
- volumes/up
- volumes/down
- folder/up
- folder/down
Automate your deployment pipeline. Every time you push up new code with code/up also minify javascript and css and sync it up as well:
before:
# Before deploying code by Git, please:
code/up:
# 1. Run your NPM production build
- "npm run prod"
# 2. Sync the results of the build up
- "php craft copy/folder/up production web/build/prod -i=0"Here is a full config file example: config/fortrabbit.example.yaml
There is also a command to create a local copy of your database to a file. You can create an .sql file and also import back such file into the database. Here is the command:
# Export DB
php craft copy/db/to-file filename
# Import DB
php craft copy/db/from-file filename
# Filename is a required parameterNote that there are also similar Craft CLI commands for this: php craft backup/db and php craft restore/db.
You can also synchronize folders which are not in Git or not an Asset Volume. A common use case is to sync up build artifacts such as minified JS or CSS to your fortrabbit App. This can be coupled with before/after commands.
# Sync up a folder from local to your fortrabbit App
php craft copy/folder/up {stage} {folder}
# Example usage
php craft copy/folder/up production web/build- The
{folder}is your relative path seen from the craft executable (project root)
You may want to run Craft Copy within any Docker container. You will need the following dependencies to be installed inside the container:
- mysqldump
- mysql (client)
- ssh (client)
- Access to the SSH keys you saved with your fortrabbit Account - for example like so
With fortrabbit you can already use Git to deploy code without any extras or plugins. When deploying code by Git Composer also is getting triggered. Craft Copy enhances on that by adding support for files that are excluded from Git such as assets in volumes, folders and database contents.
Craft Copy can help to bring together the different data types required to run Craft CMS. Each data type is unique, so is the transport layer. Here are more details so you can better understand what's going on behind the scenes:
Craft Copy offers a light weight Git wrapper. The direction will be in most case up (push code), since you will develop locally first and then push changes up to the fortrabbit App. Since Git is transport layer and version history, those changes are non-destructive. You can always roll back.
The composer.json is also managed in Git and when you push a change to that file, Composer will run during deployment on fortrabbit. That's not Craft Copy but a fortrabbit feature. So you don't need to login by SSH and run Composer manually. Also you should not trigger any updates with the Craft CMS Control Panel on the fortrabbit App itself.
Any asset files and folders, including image transformations that can be synced up and down with the volumes command. Here rsync will be used. The transport flags are set to be non-destructive. No files will be deleted and you can safely run this operation in any direction without having to fear any data loss. You might need to keep your assets library clean from time to time.
The MySQL database is getting copied over by using mysqldump. So it basically will export the current status of the database as an file.sql and will replace the other database with that file. In other words: This can be a destructive operation. You need to make sure that any content changes affecting the database, like new entries or editing entries are only done in one environment, either locally or on the fortrabbit App. It can not merge changes, like with assets or code. Good news is, that Craft Copy will always create a snapshot file which you can use to roll back.
Craft Copy creates a my.conf file. It sets some defaults to ensure maximal compability when working with different MySQL versions. See the annotated file here and read about SUPER priviliges here.
The setup is usually straight forward when the system requirements are fulfilled. However, depending on your local setup, you may run into errors. Many errors are MAMP related and easy to fix:
php craft install/plugin copy
*** installing copy
*** failed to install copy: Craft CMS can’t connect to the database with the credentials in config/db.php.Fix: Ensure "Allow network access to MySQL" is ticked in MAMP.
The mysqldump client is a command line program to backup mysql databases. It is usually included with MySQL installations. Find out if you can access mysqldump:
which mysqldump
mysqldump not foundPossible fix: Add the MAMP bin path to your Bash profile:
echo 'export PATH=/Applications/MAMP/Library/bin:$PATH' >>~/.bash_profileFind out the php version on the command line:
php -v
PHP 7.0.8 (cli) (built: Jun 26 2016 12:30:44) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
with Zend OPcache v7.0.8, Copyright (c) 1999-2016, by Zend TechnologiesFix: Add MAMP php bin path to your Bash profile:
echo 'export PATH=/Applications/MAMP/bin/php/php7.2.1/bin:$PATH' >>~/.bash_profileWhen installing the plugin via Composer you may see an error like this:
composer require fortrabbit/craft-copy:^1.0.0
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for fortrabbit/craft-copy ^1.0.0 -> satisfiable by fortrabbit/craft-copy[1.0.0].
- Conclusion: remove symfony/console v3.3.6
- Conclusion: don't install symfony/console v3.3.6
- fortrabbit/craft-copy 1.0.0 requires symfony/yaml ^4.1
[...]
Problem 99Fix: Update all existing dependencies:
composer config platform --unset
composer update
php craft migrate/allYou see a warning like this when trying to deploy:
In PluginManager.php line 762: fortrabbit/craft-auto-migrate contains a Composer plugin which is blocked by your allow-plugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.fortrabbit/craft-auto-migrate [true|false]" to enable it (true) or disable it explicitly and suppress this exception (false) See https://getcomposer.org/allow-pluginsThat's a new Composer security policy in action and should only happen when you installed the plugin a while ago.
Fix: Configure Composer to allow plugins:
composer config --no-plugins allow-plugins.fortrabbit/craft-auto-migrate true