bedrock

or the WordPress boilerplate of the same name https://github.com/roots/bedrock

You can aim to run a truly stateless wordpress container using https://github.com/roots/bedrock for the wordpress install together with Composer and https://wpackagist.org/ to manage your plugins and dependencies. Then there's https://github.com/deliciousbrains/wp-amazon-s3-and-cloudfro... to offload all media files to S3 (consider putting a Cloudfront distribution in front to get a custom domain + HTTPS). I've been there and I can't honestly recommend it. You'll be on your own. Also, it really really feels like Wordpress wasn't made to be deployed this way. If I were you I'd rather use a good hosting provider like WPEngine and spend my time on more valuable things.

That one was more a "I wonder if I can.." than a required thing so I didn't fully give it a go. I was giving Bedrock[1] a try for it which may have complicated matters further trying essentially to learn two new things at once. I imagine my thought process at the time was "Flynn is like Heroku and Heroku is all about 12 factor apps. Bedrock seems to be a 12 factor WordPress, I'll try that!". It also somewhat matched up with the rest of what I do in Laravel so the standard composer, PHP, .env, MariaDB vibe. I'll give it another shot over the weekend, I don't recall what stopped it working. Major thanks on adding MariaDB support by the way, I know mysql and the likes get their fair share of flak but it's what I've used for the past decade or so, more comfortable with it than postgres :) [1] https://github.com/roots/bedrock

Stateful? https://github.com/roots/bedrock

Does this plays nice with a modern wordpress stack like bedrock or any 12factor wp? https://github.com/roots/bedrock

The autoloader is required in wp-config to get access to Dotenv: https://github.com/roots/bedrock/blob/master/wp-config.php#L... But in the example you gave, ideally your custom plugin is itself a Composer package which requires Guzzle in its composer.json file. Then you'd require your plugin in the project's composer.json :) Re: Capistrano. We're really trying to encourage people to fork this and modify it to their needs. So you could easily rip Cap out and integrate Fabric in your own fork. We're just providing some sensible defaults that we're familiar with.

It's being used in production for roots.io right now but it's still a work in progress. Seems like your issue has to do with your symlink setup. We don't need to do any special configuration with the web server. Here's the configuration that deals with app/: https://github.com/roots/bedrock/blob/master/config/applicat...