wipeout wrote:
Would you agree with my logic?
No, because you said you only have "a couple of websites".
Control panels are useful when you have dozens of websites belonging to several customers on the same server, and when you're constantly adding or removing customers and their sites. Almost every commercial and free control panels, from cPanel to Kloxo to Virtualmin to ISPConfig, are designed for this scenario.
When you're running just a couple of sites, it's usually much easier to grab some StackScripts or follow a tutorial in the Linode Library. Modern Linux distributions such as Ubuntu make it very easy to deploy web sites. Enabling SSL and other "intermediate-level" tasks are also as simple as copying and pasting a few lines of code from the Linode Library. These tutorials were written by pros, and other pros have confirmed that they work. Besides, if you can follow a tutorial on a control panel vendor's website to install the control panel in the first place, you can just as easily follow a tutorial in the Linode Library.
Control panels might also introduce security weaknesses. Most control panels are accessible over the web, and they need to run with root privileges in order to modify the system. So any security bug in a control panel can have disastrous consequences. However, since most control panels operate separately from the operating system's built-in update procedure (such as "apt-get update"), it is not easy for a novice user to keep a control panel up to date unless the control panel knows how to update itself. Also, most control panels are accessed using passwords, which are inherently less secure than public key-based SSH logins.
Besides, how often do you plan to add new sites or make drastic changes to existing sites? You probably won't be touching anything for months, once the server has been set up. Any day-to-day changes to the websites themselves will normally take place over FTP or SSH/SFTP, which bypasses the control panel. So the control panel will just sit there, doing nothing, all the while consuming server resources and exposing a public login page that is only a password away from root access.