junaidbhura - Mar 2, 2018Hey there! I'm the author of the Auto Cloudinary plugin. I'd just like to say that the configuration guide is not obsolete, it just uses a different technique than this post. I've added a comment on your rating here: https://wordpress.org/support/topic/please-update-instruction/
I'd like to see some of the missing images of this article.
I am quite happy with the performance improvement to my WordPress hosting in Azure. After I put all the measure for performance improvement
Change default application settings Create .user.ini to override php.ini settings Use AutoOptimize plugin (and web cache) Use CDN as reverse proxy cache Read my previous blog here - blog.libinuko.com/2017/11/23/troubleshooting-wordpress-multisite-hosting-in-azure/. I analyse from the report that actually there are room for improvement in the image processing. With current configuration, all image processing will be done in the Azure hosting, and all of images will be served from my Azure app services.
Hosting single site WordPress in Azure is straight forward. With few clicks in Azure portal, your blog will be up and running easily. While moving my blog to Azure I face issues but managed to resolve it. So let see the issues:
The issues Slowness This is one of the most nightmare that every blogger tried to avoid, the slowness. The default settings provided by the template doesn't provide optimum performance.
In part 1, I elaborate what was the challenge in SharePoint default configuration and the default response header produced by WFE. Part-2, I will show how to clean response header and add additional layer of protection. From standard SharePoint deployment, we add a reverse proxy that will act as medium between the user (external client) and the SharePoint farm. So our diagram will change as follow: In computer network, a reverse proxy is a type of proxy server that retrieves resources on behalf of a client form one or more servers.
I am personally not fan of Apple who wants to queue overnight for the first release of the device - but, I am a Microsoft's fans. Especially when it deals with Microsoft SharePoint including the cloud version known as Office 365. Sometimes it is thrilling to get the first release, because we may encounter unexpected bug. In the past we saw some hiccup to early adopters of SharePoint patches. But who cares, the statistic still shows that the probability of this kind regression is low.
I have been using their service since 1 year ago, but I forget to put in my blog until last week they notify about my SSL certificate expiration. Eventually I forget all the steps to create the certificate - but I manage to renew my SSL certificate for another year for FREE! Before going further, let me confess that I am using StartSSL PKI. I stumbled upon their offer after googling to find economical SSL certificate creation.
Many of our folks in the field rely on SharePoint Farm Version number information in Central Administration to compare the patch level between servers. While this number is showing the latest SharePoint Foundation, it doesn't always mean that you have a completely patched SharePoint farm. The reason, because Microsoft releases many different type of patches:
Cummulative updates (CU) Server packages (Uber packages) Public updates (PU) Stefan Gossner wrote an excellent blog about SharePoint patch terminology and the impact your farm patch level in “SharePoint Patching Demystified” .