Statamic tuning

# Adding domains

At the beginning you have probably been using the App URL as your domain. You can also add any number of domains to your App. Please see our domain articles for more.

# Environment variables

Statamic comes with a predefined .env file. It includes what you'll need to run Statamic locally. Bear in mind that the .env is ignored in Git.

If you have not chosen Statamic as the software preset for the app, you may need to set some environment variables. Go to your environment in the dashboard, and under settings find "ENV vars". You will be presented with a textarea to put in your "Custom ENV vars". Have the same APP_KEY locally and on the App (copy from your local installation).

APP_KEY=(copy what you have locally)
APP_ENV=production
APP_DEBUG=false
APP_URL=https://{{app-env-id}}.frbit.app
shell

Please also see the ENV vars topic to learn more about this kind of configuration and implementation at fortrabbit.

# ENV vars for Statamic MySQL setup

MySQL access will be configured via ENV vars as well. Copy/paste this additional setup into the environment variables form in the fortrabbit Dashboard:

DB_CONNECTION=mysql
DB_DATABASE=${MYSQL_DATABASE}
DB_HOST=${MYSQL_HOST}
DB_PASSWORD=${MYSQL_PASSWORD}
DB_PORT=3306
DB_USERNAME=${MYSQL_USER}
env

It maps the keys Statamic is expecting to dynamic ENV vars provided by fortrabbit.

# Root path

This setting again is only required if you have not chosen Statamic with the software preset. Statamic is a Laravel application. So the root path needs to be set to public. This should be set already if you have chosen the Laravel software preset.

# Working with the Control Panel

Statamic - like other CMS's - has a control panel. That dashboard enables you - or maybe the client/editor - to create and edit the contents easily in the browser. You can create different users (admins) for the control panel.

• {{app-env-id}}.frbit.app/cp

For this, please consider how you are dealing with the content created:

• You should really not use the control panel on the App if you have all content stored in Git: you should only change things locally.
• When using rsync (or SFTP) you can sync changes you have made on the App directly back down or the other way around.
• When using MySQL as a data store, you might want to dump the production database and bring it back locally from time to time

# Using the Statamic CLI

Statamic has an installer CLI, which can be installed as a global composer package. You can use that on the environment, but it is not recommended to do so. Install Statamic locally, then deploy.

• statamic.dev/installing/local

# Continuous development

We recommend to always develop locally first — it's just the most convenient way. Deploy when you have reached a certain state of development. In many cases the "real" content will be created on the fortrabbit App. You can easily sync down changes from production into development with rsync or sftp unless you have the content in MySQL.

# Backups

Backups are available as an optional component. You can also spin your own solution. With Git you can already easily roll back changes.

# Updating Statamic

We recommend updating your local development environment first. On your local computer execute composer update in the terminal at the root level of your project folder to trigger the update. When you have confirmed that everything works, git push to bring the latest updates to your fortrabbit App.

# Sending mails

fortrabbit does not support sendmail, so sending e-mails out of the box might not work. Statamic provides config for transactional mail providers, or you can use a plugin to send e-mail over your own SMTP account.

# Getting a license

Remember that Statamic is free for personal use. For a client project, get a license, support the authors!