Drupal Frequently Asked Questions (FAQ)
If you don’t want to do so manually, include the following lines in your deploy hook in
drush -y updatedb drush -y config-import
That will automatically run
update.php and import configuration on every new deploy.
The above configuration is included by default if you used our Drupal example repository or created a project through the management console.
Normally, this means there is a problem with the MySQL server container and you may need to increase the storage available to MySQL to resolve the issue. Ballooning MySQL storage can be caused by a number of items:
- A large number of watchdog entries being captured. Examine the watchdog logs and resolve the errors reported.
- Cron should run at regular intervals to ensure cache tables get cleared out.
- You are using database caching. That is not recommended, primarily because it can easily balloon the size of the database. We recommend Redis caching for all Drupal sites.
If you are having a problem connecting to the database server, you will need force a redeployment of the database container. To do so, you can edit the service definition to add or remove a small amount of storage and then push.
For Drupal sites, the name of the session cookie is based on a hash of the domain name. This means that it will actually be consistent for a specific website and can safely be used as a fixed value.
If you see a bare “File not found” error when accessing your Drupal site with a browser,
you’ve pushed your code as a vanilla project but no
index.php has been found.