Environment Variables¶

The configuration is exposed via the following environment variables (where DATABASE is the upper-cased version of the key defined in the relationship above):

• DATABASE_URL: The database URL (in the PHP or Go format depending on your application)
• DATABASE_SERVER: The database server
• DATABASE_DRIVER: The database driver
• DATABASE_VERSION: The database version
• DATABASE_HOST: The database host
• DATABASE_PORT: The database port
• DATABASE_NAME: The database name
• DATABASE_DATABASE: Alias for DATABASE_NAME
• DATABASE_USERNAME: The database username
• DATABASE_PASSWORD: The database password

Connecting to the Database¶

1

$ symfony sql 'SHOW TABLES'

Importing Data¶

Export your database in an SQL file or in a compressed file and import it via the following command:

1

$ symfony sql < database.sql

Exporting Data¶

Dump data stored in your SymfonyCloud database via the following command:

1

$ symfony db:dump > database.sql

Timezone¶

The system timezone is set to UTC by default. Change it for the current connection with SQL SET time_zone = <timezone>;.

Multiple databases¶

If you are using version 10.0 or later of this service it is possible to define multiple databases as well as multiple users with different permissions. To do so requires defining multiple endpoints. Under the configuration key of your service, there are two additional keys:

• schemas: This is a YAML array listing the databases that should be created. If not specified, a single database named main will be created.
• endpoints: This is a nested YAML array defining different credentials. Each endpoint may have access to one or more schemas (databases), and may have different levels of permission on each. The valid permission levels are:
  • ro: Only SELECT queries are allowed
  • rw: SELECT queries as well INSERT/UPDATE/DELETE queries are allowed
  • admin: All queries are allowed, including DDL queries (CREATE TABLE, DROP TABLE, …)

Consider the following illustrative example:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

# .symfony/services.yaml
mysqldb:
    type: mysql:10.2
    disk: 2048
    configuration:
        schemas:
            - main
            - legacy
        endpoints:
            admin:
                default_schema: main
                privileges:
                    main: admin
                    legacy: admin
            reporter:
                privileges:
                    main: ro
            importer:
                default_schema: legacy
                privileges:
                    legacy: rw

This creates a MySQL/MariaDB service named mysqldb which has two databases, main and legacy. There will be three endpoints created. The first, named admin, will have full access to both databases. The second, reporter, will have SELECT query access to the main DB but no access to legacy at all. The importer user will have SELECT/INSERT/UPDATE/DELETE access (but not DDL access) to the legacy database but no access to main.

If a given endpoint has access to multiple databases you should also specify which will be listed by default in the relationships array. If one isn’t specified the path property of the relationship will be null. While that may be acceptable for an application that knows the name of the database to connect to, it would mean that automated tools such as the Symfony CLI will not be able to access the database on that relationship. For that reason the default_schema property is always recommended.

Once those endpoints are defined, you need to expose them to your application as a relationship. Continuing with our example, this would be a possible corresponding block under relationships:

1
2
3
4
5

# .symfony.cloud.yaml
relationships:
    database: "mysqldb:admin"
    reports: "mysqldb:reporter"
    imports: "mysqldb:importer"

This block defines three relationships, database, reports, and imports. They’ll be available as environment variables with the DATABASE_, REPORTS_, and IMPORTS_ prefixes. Use those to connect to the appropriate database with the specified restrictions.

If no configuration block is specified at all, it is equivalent to the following default:

1
2
3
4
5
6
7
8
9

# .symfony/services.yaml
configuration:
    schemas:
        - main
    endpoints:
        mysql:
            default_schema: main
            privileges:
                main: admin

Advanced Configuration¶

For version 10.2 and later, some MariaDB configuration properties from the my.cnf file can be customized:

1
2
3
4
5
6
7
8

# .symfony/services.yaml
mysqldb:
    type: mysql:10.2
    disk: 2048
    configuration:
        properties:
            # size in Mb (defaults to 16)
            max_allowed_packet: 64

Note that increasing the size of the maximum packet will also automatically decrease the max_connections value. The number of connections allowed will depend on the packet size and the memory available to the service. In most cases leaving this value at the default is recommended.

Troubleshooting¶