SymfonyCloud allows you to completely define and configure the topology and services you want to use on your project.
Unlike other PaaS services, SymfonyCloud is batteries included which means that you don't need to subscribe to an external service to get a cache or a search engine. And that those services are managed. When you back up your project, all of the services are backed-up.
Services are configured through the
.symfony/services.yaml file you will
need to commit to your Git repository. This section describes specifics you
might want to know about for each service.
Here is an example of a
1 2 3 4 5 6 7
database1: type: mysql:10.1 disk: 2048 database2: type: postgresql:9.6 disk: 1024
In order for a service to be available to an application in your project
(SymfonyCloud supports not only multiple backends but also multiple applications
in each project) you will need to refer to it in the
The name you want to give to your service. You are free to name each service as you wish (lowercase alphanumeric only).
Because we support multiple services of the same type (you can have 3
different MySQL instances), changing the name of the service in
services.yaml will be interpreted as destroying the existing service and
creating a new one. This will make all the data in that service disappear
forever. Remember to always snapshot your environment in which you have
important data before modifying this file.
type of your service in the following format:
disk attribute is the size of the persistent disk (in MB) allocated to
the service. The default minimum disk size is 16MB but each service can
redefined this minimum if necessary.
For example, the current default storage amount per project is 5GB (meaning
5120MB) which you can distribute between your application (as defined in
.symfony.cloud.yaml) and each of its services. For memory-resident-only
services such as
redis, the disk key is required and will
generate an error if present.
Currently we do not support downsizing the persistent disk of a service.
Services are exposed to the application using environment variables.
See the Relationships section of the
documentation for more information.
Connecting to a service¶
Once a service is running and exposed as a relationship, its appropriate credentials (host name, username if appropriate, etc.) will be exposed through environment variables. The exact names are documented on the appropriate service's page.
Be aware that the environment variable names are fixed but their values may change on any deployment or restart. Never hard-code connection credentials for a service into your application. You should use the environment variables every time your script or application starts.
To connect to a remote service from your local computer, the easiest way is to use the Symfony CLI to open an SSH tunnel:
1 2 3
$ symfony tunnel:open # Get connection information and credentials: $ symfony tunnel:info
tunnels command to list all open tunnels:
$ symfony tunnels
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.