Replacing Apache in your VPS with Nginx

If you have not been following the web development scene recently, you need to know that Apache is being seriously challenged by Nginx in the ideal server candidate position. Nginx is a great server daemon that also uses much less resources. Recently I attempted to make a move to Nginx from Apache. But there were some issues that needed to be addressed.

Well, setting up Nginx is really straightforward, just run

# apt-get install nginx

But you might face problems with starting the nginx service. Well, the most likely reason probably is that by default Nginx is configured to run on Port 80. In computers one port cannot be used by multiple programs at the same time. But Apache too is configured to listen on port 80. Now, if you want to move to Nginx and serve all your sites via Nginx, you can unassign Apache from port and give Nginx the instruction to listen to port 80. To do that you will need to tweak an apache configuration file. This may be different for different distros and scenarios but the most common place to look for the Apache configuration files is

/etc/apache2

or

/etc/httpd

Now usually the configuration can be found in

/etc/apache2/apache2.conf

or

/etc/httpd/httpd.conf

Just open your appropriate configuration file and try to find the the line:

Listen 80

If you can't find the line it's very much possible that the port instruction is in different file. Just read through the configuration and try to find if any "Include" directive. It could be like

Include "ports.conf"

Which means the port Listen directive is there. Open the file (you should be able to find that in the same directory).
Now change "Listen 80" to "Listen 1234". This will make Apache listen to port 1234.
Now you should restart Apache with

#servicectl restart apache2

And start nginx with

#servicectl restart nginx

Wordpress to survive the most difficult hurdle

A legend in the making. Wordpress, as popular as it is among content writers, it is also one of the most cubersome platforms to deploy on. And when it comes to merging more than one wordpress sites, the biggest hurdle is the Database. Well, VersionPress is coming to the rescue.

What VersionPress (VP) attempts to do is make the whole Wordpress installation version controllable. Now, it's one thing when you are merging files but it's completely different monster when you want to take on the Database. Sure, merging 2 DB dumps cannot be an issue for git but what about context?

Imagine this scenario where you have developers making your site look and work awesome and content writers writing away on live production server. Now the day comes when you have to pull the changes from the development version to the production. Well several things get intertwined here

• Posts having same IDs
• Plugins having custom tables
• Options and Meta

Now that's a real spaghetti you got there. When you think about it, you feel like nothing short of a magic is going to be needed for that right? Well, if that's so, VersionPress is magic. Here's how they are supporting plugins in their new alpha. If you are late to the show, you might want to read their past release notes too.
https://github.com/versionpress/versionpress/blob/1036-plugin-support/docs/Plugin-Support.md