Lizquilty security scaling highend hosting for wordpress

347 views

Published on

WordPress conf slides

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
347
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Lizquilty security scaling highend hosting for wordpress

  1. 1. Scaling & High End Hosting for WordPress By Liz Quilty
  2. 2. There is no single solution
  3. 3. Work out what You Want and Need!
  4. 4. Lots of articles exist already, read them! Plug-ins •  WP-Sentinel •  WordPress Sentinel (they are different!) Permissions Version Control - CVS, SVN, Git Backups! Security
  5. 5. Set Apache to ignore .svn .git .cvs, etc Ignore files •  wp-config.php •  wp-content/uploads/ •  wp-local-config.php capistrano for deploy Develop/test on local or Dev machine Version Control System
  6. 6. •  NGINX + phpFCGI ? •  Varnish + apache + mod_php •  PHP-APC •  WP-Supercache/W3-total-cache •  Batcache / Memcached •  Enable the WordPress Object Cache define(ENABLE_CACHE, true); Watch for PHP-CGI/FCGI memory usage! Scaling Single server
  7. 7. Videos - Youtube,Vimo Files - CDN, Flickr, DropBox, S3 Comments - IntenseDebate, Discus These help save disk & IO, resources Take Media Offsite
  8. 8. Cost Space Redundancy Control - or lack of it Openstack Cloudmin Control Panels? What Control Panels! The Cloud?
  9. 9. Same as Single .. plus more DNS Round Robin ? Heartbeat IP Failover ? Separate DB server w/ Replication ? File replication ? Controlling multiple servers ? Multiple Layouts - Planning is key! Scaling Multiple
  10. 10. Database: •  Mysql Master/Master replication •  Mysql Master/Slave •  Separate DB server(s) •  HyperDB Plugin DB Replication
  11. 11. •  Unisen •  rsync •  bitpocket •  DRBD •  Rsync •  Gluster Replication of Files
  12. 12. CFEngine Puppet ClusterSSH #!/bin/bash HOSTS="machine1 machine2 machine3 machine4"; if [ $1 ];then for i in $HOSTS; do ssh $i "$@"; done fi Controlling servers
  13. 13. 10 Plan 20 Test 30 Adapt 40 Goto 20 Implement Don't wait until you have a problem to test it! Monitoring - NewRelic, Nagios, etc Failover Plans, like Heartbeat, DNS, etc Have a Plan, test it
  14. 14. Backup! Backup! Backup! Multiple Sites for redundancy Documentation in case developer/admin disappears Things to remember
  15. 15. Questions? Questions?
  16. 16. http://www.freesoftwaremagazine.com/articles/easy_file_sync_bitpocket

×