Deploying Django on VPS is an easy task if and only if you know some system administration tasks. You may think on which I have written this statement. But believe me, it’s my personal realization when I deploy my personal blog (made on Django). Let’s go back. Previously, my personal site was on WordPress, a PHP based CMS. It is free, Open Source and the top blogging CMS.. Everything was going right.
Last 2 years, I am using runit to run any script automatically during booting. When I was using Ubuntu 14.04 in my server, I wasn’t having any issue. But in Ubuntu 16.04, an issue has been found. runit plays with upstart which was default in Ubuntu 14.04. But in Ubuntu 16.04, upstart has been replaced with systemd. So, runit isn’t working normally. But the issue can be fixed as follows:
MariaDB is an enhanced, drop-in replacement for MySQL offering many speed improvements intended to remain free under the GNU GPL. MariaDB version numbers, up to 5.5, followed MySQL’s numbers. Thus, if one uses MariaDB 5.5 one knows that all features from MySQL 5.5 are available. After version 5.5, MariaDB developers decided to start a branch numbered 10, as an attempt to make it clear that MariaDB 10.0 will not import all features from MySQL 5.
By default, Sentora, as well as Sentora, comes with Apache 2.2 and I feel that it’s a bad solution when there are many good solutions already for using as web server e.g. Litespeed, NginX, Lighttpd etc. Litespeed is a paid service so I never use it at all. If you have the ability to pay for it, you should use it as it is very good as far as I see on Benchmark test results.
Hello readers! After a long time I am back with a new topic. Today I am going to discuss about cPanel bandwidth problem. The websites on your server may use heavy traffic but cPanel bandwidth counter always show that they are using a low bandwidth. Then you can understand that cPanel can’t count bandwidth correctly. Actually we get this issue when we try to use Nginx/Varnish as a web-proxy in front of Apache.
When you install CentOS on your server then your default SSH port is 22. It’s default, I mean, all servers with CentOS operating system normally have port 22 opened. Any hacker may flood this port or try to connect via this port and can do any harm to the server. So the better practice is to change the port. Though it can’t do much for you, but I believe that it’s quite impossible to find out a SSH port for a hacker where the appropriate range is too long to guess the correct port.
If you are using a VPS and you have cPanel installed on it, then you may need to update or change WHM Nameserver IPs for various reasons. If you simply try to change it, you will find that they are not changing accurately. For this, you have to do it manually I mean you may do it by command. Login to your server via SSH, you need to log in as root.
- NEWER POSTS
- page 2 of 2