The configuration file is kept as generic as possible on Heroku, add-ons JawsDB (for MySQL), Bucketeer (for S3 storage), and SendGrid (for E-Mails) are used. This means that the installation of plugins and their configuration can be part of your version controlled code, so you can easily re-create a blog installation without any manual steps that need separate documentation.

After a deploy, a set of pre-configured Composer scripts can run several administrative functions using WP-CLI, such as initially configuring the blog, and enabling plugins (this happens either automatically when using a Heroku button deploy, or manually). WP-CLI is used for easier (or automated) handling of tasks such as enabling plugins or storing configuration options. See further below for information on how to update WordPress versions. What you deploy is what gets executed, which makes setups simple to deploy, and, most importantly, reproducible. Locally bundled custom themes and plugins from top-level themes and plugins directories can be referenced for inclusion via composer.json and will be linked into wp-content.Īutomatic updates for WordPress or plugins, and theme editing, are disabled intentionally. A wp-config.php resides in the root of the project, and uses several different environment variables to control behavior. The WordPress installation is fully contained in top-level wordpress and wp-content directories upon composer install. WordPress, the Twelve-Factor way: fully managed using Composer and configured using environment variables.

Directory wordpress theme 2017