a DevSecOps engineer from Brazil 🖖
Since version 4.4, WordPress has a native responsive image support by including srcset and sizes attributes to the image markups. It's a good function, no doubts.
However, it can cause problems which you are probably have, if you are reading this.
In my case, I convert my blog from a local WordPress installation using HTTrack. As for today, HTTrack can't recognize those attributes, then, some images weren't being showing for my readers.
Since the update 11.58, I noticed that cPanel NAT solution wasn’t working with Apache on Amazon Web Services and Google Cloud Engine.
Apache was using the public IP on the VirtualHost instead of the instance local IP address and that does not work on providers that performs NAT outside the VM scope.
This is an old article, currently I'm using Publii (read here)!
Static websites are faster than WordPress installations. However, I am tech enthusiast and I love a challenge. I'm well aware of Jekyll's existence, but I love WordPress.
Since my blog doesn't have any dynamic content besides the comments, I decided to go for it.
There are plenty reasons why you shouldn't do that, here’s a few:
1. Very difficult to scale;
2. Difficult to edit;
3. Just for static content.
However...
On the 28th November, I will be hosting a workshop named "In the cloud like a boss" at PUC Consolação in Sao Paulo, approaching everything you need to know, from hypervisors and storage technologies to tweaks on wp-config.php and more. The slides will be made available…