Jaan Paljasma | Tech Blog

As announced today, Google PageSpeed Service PSS (which has been in beta since July 2011) will be shut down forever on August 3, 2015. For every site currently using PageSpeed Service, you must change your DNS before 3rd August 2015 or your site(s) will become completely unavailable on that date. If you wish to continue enjoying many of the performance benefits of PageSpeed Service, the same Google PageSpeed technology is available in a number of alternative packagings which you may wish to consider using, including Apache mod_pagespeed, and nginx ngx_pagespeed. Other cloud-based solutions are available, too. Read more on Google PSS .

For quite a while now I have been trying to exploit AWS OpsWorks to deploy software updates to our MetaSearch Gateway with less manual work. Before using OpsWorks, I built AWS servers from custom AMI, deployed app using git push to remote, and remote deployment hook pulled latest code updates to a folder; and if there were any secondary servers, these were updated with rsync. Now, AWS OpsWorks is great set of tools, based on famous Chef (currently 11.4 is supported). With little efforts I was able to include and configure necessary PHP extensions to a default PHP Web app: APC memcached Mongo Geoip Since AWS supports also elastic load balancer, I have two 24/7 instances running behind ELB, and third server (load-based) waiting for load to increase. Deployments are quite easy, with a push of a button, code is pulled from remote git and symlinks are updated. Sounds good? Well, too good to be true. By default, after deploying your app, Apache restarts itself; and naturally this c...