Nginx

Today I was eager to install and enable really cool Drupal module for my blog - Social Share Counter, this module looked simple - all I had to do, just download, enable and a little bit tweak around. From module creator (s) This module gives the share counts for only Facebook,Twitter and more which has some excellent features in more elegant manner. If you have a website, then you definitely need this module. Unfortunately, after I successfully installed and enabled this module I noticed…

That day finally have come and I've officially started a new project on my first Drupal 8 website. While my first attempts were about two years ago, but due to the lack of time and will to explore new things and configure new servers I proceeded just tonight (after a conversation with a long time customer we agreed to make a re-branded website and I was allowed to "experiment" with a Drupal 8 site) I took me some time to get it running as I wasn't prepared for the Drupal 8 requirements, and…

In this tutorial you will learn how to setup a LEMP stack on Ubuntu 12.04 for serving a Drupal site (s). Update: I originally started this post to document my setup for actually configuring Nginx server on Ubuntu for Drupal site at the start of 2015. Many things have changed ,ever since, thus most of the written bellow will work. LEMP is a variation of the ubiquitous LAMP stack used for developing and deploying web applications. Traditionally, LAMP consists of Linux, Apache, MySQL, and PHP.…

Free SSL certificates from Let's Encrypt certify are issued for a short 3 month term. I first enabled secure HTTPS pages around at start of 2016, and now it's time to renew SSL.  The following tutorial is written for Nginx, but should work for Apache as well (with minor modifications) Stop Nginx​ sudo service nginx stop To trigger the renewal process for all installed domains, run this command: sudo /opt/letsencrypt/letsencrypt-auto renew Start Nginx ​ sudo service nginx start Now,…

Encrypted HTTPS websites are pretty much a hot topic nowadays. I have seen a lot noncommercial websites and blogs using HTTPS protocol lately.  I believe cheap prices for certificates and possible SEO boost from Google are pushing more and more to add HTTPS. Including me! In fact this article is first since my blog is HTTPS, to celebrate that I decided to write shot tutorial how you too can enable HTTPS on Ubuntu 12.04 running Nginx and optionally running a Drupal site on Linode VPS.…

The other day I visited tools.pingdom.com to test performance for my blog (the one you are currently reading) and I did fine I have a two bottlenecks: Remove query strings from static resources Specify a Vary: Accept-Encoding header I managed to handle query string issue for static resources and then I headed to find a solution for the Specify a Vary thing. Since it's not a Drupal related issue I did some search regarding Nginx and I soon found excellent solution on stackoverflow.com How to…

After a long period of doubts should I start testing and developing with Drupal 8, which stable version is not yet released, yesterday I decided to give a try for a Drupal 8 beta release. I bought a new Linode VPS, quickly deployed there Ubuntu 14.04, and installed Nginx as a web server. I did it because my current server is PHP 5.2, and Drupal 8 is asking for at least PHP 5.3. So  - not to mess up with my existing server configuration, a new Linode seemed the best option.  All went pretty…

Redirecting website visitors to a different domain name using Nginx is simple. Add the following code to your server config:  server { server_name .domain.com; return 302 $scheme://forwarded-domain.com; } Restart Nginx sudo /etc/init.d/nginx restart

If you have ever encountered an error message that says "Nginx: 413 Request Entity Too Large", you know how frustrating it can be. This error message usually pops up when you try to upload a file that is too large for your server to handle. The good news is that it is possible to fix this error message. In this article, we will discuss some methods you can use to solve the "Nginx: 413 Request Entity Too Large" error. Here are some solutions to fix the "Nginx: 413 Request Entity Too Large"…