I’ve been playing with Python for close to two years now. I started out playing with Python when I had a need to develop web applications faster. I was getting rather bored with the additional development time that the thousands of lines of XML and the constant restarting of Tomcat that the Java, Struts, Hibernate, et al. stack was adding to my workload. Anyway, at the beginning of my Python journey, I began evaluating a few different Python web frameworks. After these couple of years, I’m ready to record a few of my thoughts on the process.
I was pretty excited to see an update to WP-Cache. The first thing I noticed is that when I enabled the new super cache compression option, I started getting a file save as dialog instead of my pages. As of the current version of WP-Super-Cache, the readme.txt file states that if you get this, you need to disable the super cache compression option.
Not being satisfied with this answer, I’ve done a little digging and come up with the following solution. Continue reading “Making WP-Super-Cache gzip compression work”
I posted a while back on getting Heartbeat set up to add reliability to websites. After a few weeks of experience with the system, I thought I’d add a few additional tips on making the setup more reliable. There are already a few good guides on getting heartbeat set up. You could also read my original post on the subject if you don’t already have heartbeat load balancing your site. This post however, deals with the case when you are servicing more than one site per physical server.
We host three different websites on three different physical servers. Each physical server hosts two websites with Apache. Each website is hosted on two different physical servers. The sites are load balanced with ldirectord which resides on two different servers that manage the public IP addresses to our services with Heartbeat. If load increases on any of our services, we could always add additional physical servers relatively easily.