Trellis 1.0.0 has finally been released. It's been a long and exciting path since the very first commit on Apr 16, 2014 (back when it was first called bedrock-ansible!). That was so long ago the project started on Ubuntu 14.04 and PHP 5.5.
Trellis now has a slimmer configuration file. Lots of settings have been moved outside of the configs and have intelligently set proper defaults.
Trellis now comes with automated Let’s Encrypt integration for free SSL certificates and the best HTTPS setup. Scores an A+ on the SSL Labs Test.
Follow up to the 'Improving WordPress Password Security' post. If you’re on PHP 5.5+ then use our bcrypt plugin to improve your site’s security.
We’ve released the wp-password-bcrypt plugin to improve WordPress password security by using bcrypt instead of insecure MD5 password hashing.
Trellis 0.9.1 introduces MailHog for capturing emails during development, customizable timezones, and bug fixes.
Trellis, formerly bedrock-ansible, is our latest project. Use Trellis to create and manage more professional server environments almost automatically.
Trellis now has built-in deploys instead of needing to use Capistrano. We’ve preserved the best part of Capistrano while keeping it simpler.
Bedrock 1.1.1 introduced a web subdirectory for your WordPress application, auto-generating .env files, and WordPress Packagist namespaces.
Bedrock is a modern WordPress stack. Better folder structure, dependency management with Composer, easy WordPress configuration and more.
An in-depth introduction to deploying WordPress with Capistrano. If you cross your fingers before a deploy, then this screencast is for you.
Turning a WordPress site into a Twelve-Factor App. If you're going to be creating complex websites with WordPress, then you need to get serious about it.
Factor #12: Run admin/management tasks as one-off processes. Write custom WP-CLI commands to guarantee you'll have access to your WP environment.
One of WordPress' biggest failings is not providing better logs. You can investigate implementing your own logging by using WP hooks and actions.
Factor #10: Dev/prod parity. Keep development, staging, and production as similar as possible. It’s all about automating your setup.
Factor #7: Port binding. Use Nginx + PHP-FPM in production for more flexibility and much better performance over Apache + mod_php.
Twelve-factor processes are stateless and share-nothing. Issues you'll run into with making sure WordPress is stateless: sessions and uploaded files.
Factor #5: Build, release, run. You shouldn't be deploying code to production if you can't reliably rollback a deploy.
Factor #4: Backing services. The important outcome of treating backing services as attached resources is that it's mostly taken care of by a proper config.
The twelve-factor app stores config in environment variables. See how to take wp-config.php and store configuration as environment variables.
The dependency system for PHP is Composer. In the world of Composer, the dependency declaration manifest is a composer.json file in the project root.
Your WordPress site/app codebase needs to be tracked in a version control system. Git is usually the de facto choice and you can't go wrong with it.
By using the WordPress functions `timer_start` and `timer_stop`, you can setup quick performance tests without setting up a full benchmarking test suite.
See how to create Composer packages for custom WordPress plugins, along with private plugins and 3rd party plugins with the composer.json file.
This screencast gives an in-depth introduction to dependency management in PHP using Composer and more importantly, why you should use it with WordPress.