WordPress Continuous Maintenance
Download as PPTX, PDF2 likes559 views
The document discusses the considerations and best practices for using WordPress in business-critical applications, emphasizing the importance of creating efficient workflows for managing environments and server maintenance. It introduces tools like Vagrant, Ansible, and Bedrock for development, as well as a maintenance service called 'Care of WP' for continuous support and security. Additional tips highlight the need for proper hosting, updating protocols, and managing plugins to avoid complications in WordPress performance.
WordPress Continuous Maintenance
- 3. OLAF LINDSTRÖM linkedin.com/in/olaflindstrom twitter.com/Lindstromer [email protected] +46 706 10 67 81
- 4. OLAF LINDSTRÖM linkedin.com/in/olaflindstrom twitter.com/Lindstromer [email protected] +46 706 10 67 81
- 6. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, MANAGE DEV/QA/PROD ENVIRONMENTS, AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO A "PRODUCT" WHICH WE WILL ALSO GIVE A SHORT
- 7. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, MANAGE DEV/QA/PROD ENVIRONMENTS, AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO A "PRODUCT" WHICH WE WILL ALSO GIVE A SHORT
- 8. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, DEV/TEST/PROD ENVIRONMENTS AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO A "PRODUCT" WHICH WE WILL ALSO GIVE A SHORT
- 9. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, MANAGE DEV/QA/PROD ENVIRONMENTS, AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO A "PRODUCT" WHICH WE WILL ALSO GIVE A SHORT
- 10. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, MANAGE DEV/QA/PROD ENVIRONMENTS, AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO A "PRODUCT" WHICH WE WILL ALSO GIVE A SHORT
- 11. THINKING OF USING WORDPRESS IN BUSINESS CRITICAL WEB PAGES? THIS TALK WILL GUIDE YOU ON WHAT TO CONSIDER BEFORE YOU START AND ALSO GIVE HANDS ON TIPS ON HOW TO CREATE A WORKFLOW THAT MAKES IT POSSIBLE TO ROLLBACK RELEASES, ORCHESTRATE PLUGINS/WORDPRESS, MANAGE DEV/QA/PROD ENVIRONMENTS, AND HOW TO MAINTAIN SERVERS IN A AUTOMATED WAY. AT THE JÖNKÖPING OFFICE WORDPRESS GROUP WE'VE PACKAGED THIS INTO ”CARE OF WP” WHICH WE WILL ALSO GIVE A SHORT
- 13. - IS IT WORTH IT? - DO CLIENTS WANT IT? - INVESTING IN CAPITAL STRUTURE?
- 14. YES IT’S WORTH IT! - Unique advantage on WP market - Minimize risks - Shorter release cycles
- 15. YES, CLIENTS WANT IT! - Experienced clients? - Inexperienced clients? - Will it cost?
- 16. YES, WE WANT CAPITAL STRUCTURE! - Documented and good processes - Less error prone - No more “GLHF” to new employees
- 18. DIFFERENT TOOLS
- 19. VAGRANT “Create and configure lightweight, reproducible, and portable development environments.”
- 20. ANSIBLE “Automated server provisioning for development, staging & production parity.”
- 21. COMPOSER “Dependency Manager for PHP”
- 23. SCOTCH BOX - Only a development environment - LAMP-stack - Many tools
- 24. SCOTCH BOX – SERVER - Ubuntu 14.04 LTS - PHP 5.6 - Ruby 2.2.x - Vim - Node - NPM
- 25. SCOTCH BOX – DB - MySQL - PostreSQL - SQLite - MongoDB
- 26. SCOTCH BOX – TOOLS - Grunt - Bower - Yeoman - Gulp - Browsersync - PM2 - WP-CLI
- 27. SCOTCH BOX – SUMMARY - Leave the XAMP-swamp forever! - Good environment for multiple PHP- platforms: - Laravel - WordPress But no deployment/server configuration!
- 28. VARYING VAGRANT VAGRANTS - Focused on WordPress development - LEMP-stack - Setup with: - WordPress stable - WordPress trunk - Good for plugin/theme creators
- 29. VVV – SERVER - Ubuntu 14.04 LTS - PHP 5.5 - Apache - Opcache
- 30. VVV – DB - MySQL
- 31. VVV – TOOLS - WP-CLI - grunt-cli - PHPMyAdmin - NodeJS
- 32. VVV – SUMMARY - Leave the XAMP-swamp forever! - Good environment for WordPress developers - Testing plugins/themes before release But no deployment/server configuration and with LAMP-stack!
- 33. BEDROCK AND TRELLIS - Created by roots.io - Open source - Many contributors/users
- 34. ANSIBLE PLAYBOOKS FOR SETTING UP A LEMP STACK FOR WORDPRESS.
- 35. TRELLIS - SERVER - Ubuntu 14.04 LTS - Nginx - PHP 5.6 or HHVM - Memcached, Fail2ban, ferm etc.
- 36. TRELLIS - DB - MariaDB
- 37. TRELLIS - TOOLS - WP-CLI - sSMTP
- 38. BEDROCK IS A MODERN WORDPRESS STACK THAT HELPS YOU GET STARTED WITH THE BEST DEVELOPMENT TOOLS AND PROJECT STRUCTURE
- 39. BEDROCK - STRUCTURE - Change /wp-content to /app - Move WP Core to /wp
- 40. BEDROCK – DEPENDENCY MANAGEMENT Composer to manage WordPress Core, plugins (and themes)
- 41. BEDROCK AND TRELLIS - SUMMARY - Targeted for WordPress on VPS - Blazingly fast LEMP-stack - Gives dev/staging/production parity - Handles deployment - Plugin/WP-core management
- 44. Deploy: ./deploy.sh <environment> <domain> Rollback: ansible-playbook -i hosts/<environment> rollback.yml --extra-vars="site=<domain>” Setup a new server: ansible-playbook -i hosts/<environment> server.yml
- 46. BEDROCK AND TRELLIS - WHAT WE DON’T GET - Deploying databases - Test routines - Centralized CI-server
- 47. CARE OF WP Packaged WordPress maintenance
- 48. MAINTAIN - and take care of hosting - a high performance - a high level of security by updating
- 49. REFINE - by working with content - by measuring with Analytics - by analyzing measured data
- 50. DEVELOP - new functionality - new sites
- 51. SMALL, MEDIUM, LARGE Defined packages Small 3h/month Medium 9h/month Large 17h/month X-Large Custom
- 52. TASKS - WordPress updates - Plugin updates - Uptime/transaction monitoring - Email/Phone support - Content updates - Etc.
- 53. SOME TIPS ALONG THE WAY • Do things “the WordPress way” • Avoid “Plugin hell”, as it will give you headache later on • Hosting should never be shared, use a VPS/Dedicated machine • Have a plan to maintain WordPress core as well as plugins, could be part of your service management agreement.
- 54. LINKS • olaflindstrom.se/kds • roots.io • Podcast • Tutorials • Discourse forum • “WordPress-utveckling” on Facebook goo.gl/E5F3X7
Editor's Notes
- #2: x
- #3: x
- #6: x
- #15: USP with having a good dev workflow! No fear of releasing, really nice!
- #16: Experienced clients or larger companies will probably understand why it’s good to have a professional way of doing things. Inexperienced clients or “small businesses” will be happy that their site breaks less often, even if they don’t understand why Really small clients might not be worth the while to work for
- #17: A capital structure makes it easier for new employees as well as colleagues to join in on the same project. It makes it possible to document workflows in a better way. No more GLHF!
- #20: “Create and configure lightweight, reproducible, and portable development environments.”
- #21: Ansible is an IT-automation tool that makes it possible to manage servers and their software. It also supports things like deployment and rollbacks. Ansible works like chef or puppet and uses playbooks to configure and setup different software.
- #22: This is how we will handle plugins, WordPress core etc. Think Node Package Manager but for PHP!
- #23: We didn’t want to invent the wheel ourselves when there’s a vivid community around WordPress. So we started looking at alternatives.
- #24: Scotch Box is a preconfigured Vagrant Box with a full array of LAMP Stack features to get you up and running with Vagrant in no time. It doesn’t give you things like server configuration/automation, deployment etc.
- #25: Server config/basic software
- #26: Some DB stuff
- #27: Some node stuff
- #28: Some node stuff
- #29: Varying Vagrant Vagrants is an open source Vagrant configuration focused on WordPress development. VVV is ideal for developing themes and plugins as well as for contributing to WordPress core because of it’s “nightly” versions.
- #30: Server config/basic software
- #31: Some DB stuff
- #32: Some node stuff
- #33: Some node stuff
- #34: We choose Trellis together with Bedrock, both created by a team called Roots.
- #35: Ansible works like chef or puppet and uses playbooks to configure and setup different software.
- #36: We choose Trellis together with Bedrock, both created by a team called Roots.
- #37: We choose Trellis together with Bedrock, both created by a team called Roots.
- #38: We choose Trellis together with Bedrock, both created by a team called Roots.
- #40: We choose Trellis together with Bedrock, both created by a team called Roots.
- #41: We choose Trellis together with Bedrock, both created by a team called Roots.
- #42: Meant to be used with WordPress, nothing else. Really fast with micro caching at the easie of setting it to true and time period. Deployment and rollbacks with Ansible. Keep development, staging, and production as similar as possible
- #43: Folder structure on our projects
- #44: Folder structure on our projects
- #45: Folder structure on our projects
- #46: Folder structure on our projects
- #48: We choose Trellis together with Bedrock, both created by a team called Roots.
- #49: We choose Trellis together with Bedrock, both created by a team called Roots.
- #50: We choose Trellis together with Bedrock, both created by a team called Roots.
- #51: We choose Trellis together with Bedrock, both created by a team called Roots.
- #52: We choose Trellis together with Bedrock, both created by a team called Roots.
- #54: Även allmäna saker att tänka på med: Förstudie/effektkartläggning Analys/mätning av kvalitet Personalisering I WP kontra t.ex. Epi eller Drupal/Sitecore
- #55: I’ve gathered some links. Make sure to visit them, you can also find a lot of good things on their site and discourse forum.