Beach

This tutorial takes you through the steps for creating a project and instance on Beach and importing existing content of a Neos website.

Accessing your project's instances for maintenance and inspection.

Connect to your MariaDB database from a remote computer.

Export a database, import existing data or clone a database from one instance to another, using the command line.

Download Flow resources from the instance's cloud storage for local development.

Configure Flow or Neos to use libvips for rendering images and thumbnails.

Using Redis with Beach projects is easy and will speed up loading times and improve the user experience of your Neos users.

When an instance is being deployed, it can execute custom scripts before it receives traffic.

You can run your own scripts in an instance: every hour, every day, or when you like.

You can run your own daemon scripts in an instance, for example for watching event loops or running job queues.

The Google Analytics integration needs persistent credentials that survive deployments.

For an automated workflow, you can let Gitlab, Github or any other tool triger builds in Beach when new commits are available.

Centralized logging helps you finding the right information and keep logs between deployments.

This guide contains all information about assigning a custom domain to your instance, obtaining an SSL certificate and setting up DNS to go live with your website.

Standard ports for sending emails are blocked for security reasons, but there are alternatives for sending mail from Neos and Flow.

This guide explains how you generate an SSH key and add it to the SSH Agent.

If you need to scale an instance up using additional replicas, there are some things to keep in mind.

Redirects on persistent resources do not work in Beach – but there's a workaround for that.

If for some reason you do not or can not use Local Beach, Sitegeist.MagicWand offers an easy way to clone production data for lcoal development – also with Beach.