Starting Linux Web Hosting Administration

They don't seem to publish them on the new website anymore, but until they launched the new site, Ubuntu was the overwhelming distro of choice among Linode customers, followed by Debian. I would actually argue that Ubuntu is more stable and secure over the long run than a rolling release OS like Debian, due to the LTS releases, which are released every 2 years (in April) and are supported for 5 years:

http://en.wikipedia.org/wiki/List_of_Ub … f_versions">http://en.wikipedia.org/wiki/ListofUbuntureleases#Tableof_versions

But Debian and CentOS are both excellent choices too, this really comes down to personal preference. For me, I like being in a Debian-like ecosystem with a fixed and predictable release schedule, and that's Ubuntu.

@Guspaz:

They don't seem to publish them on the new website anymore, but until they launched the new site, Ubuntu was the overwhelming distro of choice among Linode customers, followed by Debian. I would actually argue that Ubuntu is more stable and secure over the long run than a rolling release OS like Debian, due to the LTS releases, which are released every 2 years (in April) and are supported for 5 years:

http://en.wikipedia.org/wiki/List_of_Ub … f_versions">http://en.wikipedia.org/wiki/ListofUbuntureleases#Tableof_versions

But Debian and CentOS are both excellent choices too, this really comes down to personal preference. For me, I like being in a Debian-like ecosystem with a fixed and predictable release schedule, and that's Ubuntu.
Thanks for replying.

I could not agree more with what you said.

But regarding what I've asked for in the topic, what about it?
> Because I am asking for a plan for what to do next and what to do next? then I will follow this plan in my own and goggle it to learn as no one teaching any one but you should try it yourself.

So may some one give me a plan ? I do not mean details but just lines and I will do it in my own.

I am in a situation that I do not know what to search for? what is the term to search for?

Then I will dive more and more.

Well, a good place to start might be the Linode library:

https://www.linode.com/docs/

The quickstart guide is something to look at. There are also a few introductory articles here:

https://www.linode.com/docs/tools-reference/

"Introduction to Linux Concepts" is probably a good place to start.

Please does there is any recommended order to follow for exploring the Docs?

Since many servers are configured differently it's not really possible to follow any specific order when learning about server administration.

Learning system administration takes hundreds of hours of hands on experience; it is not a "quick read". There is no fast track to becoming a system administrator, and there is no "reading list" that I'm aware of. You can take classes (brick & mortar or online), read many books & articles, etc but you still need hands on experience. Always learn from your mistakes (there will be many; we've all made them), and always make backups of your system and even any config file you're going to mess with. No exceptions.

The very first thing you need to do is determine what you want/need your server to do and learn a general overview of how that process works. If you don't understand the flow/path of how things work then you can't figure out what will or won't work for you at one of the many stops along the way.

Below are some of the important items you need to consider; this list in not complete by any means:

• if you're going to use control panel software then you need to pick one (too many to paid & free options to list), learn how to use it and learn basic Linux command line management. Remember that it's almost impossible to remove control panel software after you've installed it. You'll need to start with a clean installation to try another one or to run your server without one.

• if you're not going to use control panel software you need to learn basic & intermediate Linux command line management.

• if you're going to be running one of the popular CMS packages, frameworks, forums, etc then you need to determine what the requirements are for your package(s) of choice and learn about them.

• if you're using Apache, nginx, lighttpd or something else as your web server software then you need to learn basic management & configuration for Apache, nginx, lighttpd or something else.

• if you're using a database like MySQL, MarinaDB, Postgres, Mongo, etc then you need to learn basic management & configuration for MySQL, MarinaDB, Postgres, Mongo, etc.

• if your website(s) use Ruby, PHP, Python, Go or something else then you need to learn how your platform of choice interacts with your web server software (eg, Apache, nginx, lighttpd, etc).

• if you're hosting email then you need to pick an MTA (eg, Postfix, qmail, Exim, sendmail, etc) and a delivery agent (Dovecot, Courier, etc). You may even need to pick webmail software (Roundcube, Squirrel Mail, Horde, ATMail, etc).

• if you use one of the hundreds of other Linux utilities or packages then you need to learn how they work, how they interact with your configuration and how to manage & configure them.

Some of these choices are made for you if you choose a CMS, framework, forum, etc. That just removes the complexity of making choices and does not remove the necessity to learn about what it takes to manage one of those options. Remember, you're not "running a website." You're "running a server that you website(s) run on." There is a difference if you actually intend to be a system administrator.

Thanks a lot Main Street James for the very useful reply.

I don't think that control panels prevent development of skills compared to the command line, but they can be a vulnerability. Web panels aren't as secure as SSH with key file auth only. If you go with a control panel, one with two factor auth to your phone or email with 2FA enabled would be best, or at least some sort of IP verification on the web server virtual host running the control panel.

A control panel could make you too reliant on GUI, and there are some things that you might not be able to do without a terminal or remote desktop.

Most people using cpanel but I do not know if it is secured or not.

Unless you need to have non-sysadmins config their own systems (i.e you're reselling web services) - control panels are a complete waste of resources - avoid like the plague.

@vonskippy:

Unless you need to have non-sysadmins config their own systems (i.e you're reselling web services) - control panels are a complete waste of resources - avoid like the plague.
you mean to deal with everything from command line even the database queries and no phpmyadmin?

@MGadAllahBasheer:

@vonskippy:

Unless you need to have non-sysadmins config their own systems (i.e you're reselling web services) - control panels are a complete waste of resources - avoid like the plague.
you mean to deal with everything from command line even the database queries and no phpmyadmin?

MySQL workbench is a better bet (or some other desktop client). It connects over SSH so it's secure and it performs well.

PHPMyAdmin can be used over SSH too, via tunnelling, either by tunnelling to the non-accessible web interface or by running it locally and tunnelling the SQL connection.

MGadAllahBasheer,

Here's a free Linux 'Intro to Linux' course (usually $2,400):

http://lifehacker.com/learn-linux-with- … 1612770920">http://lifehacker.com/learn-linux-with-this-free-edx-course-from-the-linux-fo-1612770920

That may be a good place to start.

Very informative posts Main Street James, thank you.

Jeff

@Guspaz:

PHPMyAdmin can be used over SSH too, via tunnelling, either by tunnelling to the non-accessible web interface or by running it locally and tunnelling the SQL connection.

Like using the server as a SOCKS proxy and setting the web server virtual host to only allow access from the server's IP address?

All websites today currently run on either a Windows web server or a Linux-based server. The vast majority of websites run on a Linux-based platform as Linux has a strong reputation for security and web server performance. With standard HTML-based websites, the web hosting platform doesn't make much difference. When it does make a difference, however, is when the website uses a dynamic scripting technology such as ASP , or PHP. A Windows-based hosting solution will run a Microsoft Windows server with IIS , and is necessary to run an ASP / ASP.NET scripted website. A Linux-based platform is typically used for PHP, Perl, and most other types of websites. Basically, unless your website uses ASP , Windows hosting is not necessary. If you want more information, visit Hostbuddy.com.