Tips for Unmanaged Server on Rackspace Cloud is intended for the users who want to host a small to medium website on Rackspace IaaS but can not carry the extra fee for the managed layer – at the time of writing, the cost of being managed is $100 USD extra per month. Obviously, Rackspace has their own guides or tips, but these are our tips as users.
Tips for Unmanaged Server on Rackspace Cloud : Understanding the Terminologies
The first among these tips for unmanaged server on Rackspace Cloud, will be not to go fancy with the word CLOUD and use any Cloud Server, just because you think it is something new. In other words, a complete understanding of the phrases like Cloud Computing and Cloud Computing Service models. Cloud Server is an IaaS.
May be, a PaaS like Rackspace Cloud Sites, Heroku Cloud, App Fog or Red Hat OpenShift is more than enough for your need. Rackspace Cloud Sites has advantages over Unmanaged Cloud Server for simple web hosting. You can plan to split your domains in to different server or server groups for better manageability. We wrote before, for Whom Unmanaged Rackspace Cloud Server is a Good Option.
Tips for Unmanaged Server on Rackspace Cloud is written by a person who has no degree on Server Administration but has nearly a decade’s experience; both as a Provider and User. This guide is based on that experience. Now you need to know the basics of Managed Hosting Services and Managed Servers and got to Rackspace’s official website and check their documents on Managed layer.
We wrote an article before – Where From the Middle Class Buy Cloud Services From. Rackspace, does have excellent support but possibly with the managed level, it is never for the Middle Class – Middle Class indicates the earnings from the website or rather return of investment NOT the person’s cumulative income.
Tips for Unmanaged Server on Rackspace Cloud : Choosing the Distro and RAM
The third tips will be about choosing distribution of Linux. We will, suggest to go with Ubuntu, maximum Debian. rpm based Linux are difficult to manage, Ubuntu has free community support almost as good a paid plus the components are updated regularly. It is true that, Ubuntu steals personal data (search on YouTube) as said by Richard M. Stallman, but for server; we are not installing desktop version. In other words, Ubuntu’s Privacy issues are with Desktop version, not Server version. If you have doubt, go with Debian.
One GB of RAM is more than enough for hosting normal Content Management Systems.
Tips for Unmanaged Server on Rackspace Cloud : Backup, Updating, Patching, Monitoring
Either Rackspace has own tools or gives suggestion in the usage area (usage area can be any part of the control panel, at any stage) for using some third party tools.
If you are going to make mistakes, especially with configuration files and maybe even with websites; a backup can save your life. Unmanaged hosting is a misnomer, it does not really leave you entirely alone. A certain level of support is always provided. It is quite challenging to keep the system updated and patched. You will have plenty of chances to remain vulnerable to newbie attackers and hackers. As for hosting simple HTML pages, there is possibly less risk; But actually for this 4 elements, we need a managed level.
Obviously, all of us manages the Open Source CRM like WordPress. So, it can be a good question why we will require a managed level? Just read the list (quite nicely written) :
The above webpage, not only helpful to understand what tasks to do but itself a good guide.
If a server is hacked, its more difficult to manage versus a hacked WordPress, if we do such comparison. Weigh your risks, your capabilities, your extra time needed to be invested everyday. We usually do not recommend to use an Unmanaged Server but definitely, your budget is a big factor for the decision.
Stay Hungry, Stay Foolish – may be a PaaS is a safer option for you than an unmanaged server running WordPress just for these 4 points – Backup, Updating, Patching and Monitoring; if money is the containing factor.
Follow the Author of this article :