Thor's VPS thread

[Thor]

Hello.

This is a off spin from the githelp.co.za thread.

Okey so I am getting my VPS now and would appreciate it if I can learn from you guys in the process.

Overview:

My end goal is to be less reliable on WHM + Cpanel preferably if I master this I want to ditch WHM entirely.

Things I want to be able to do:

I'd like to set the VPS up in such a way that it works like my current cpanel setup if that is possible, in other words I currently do things like this:

On WHM I create the website account I then log into the cpanel account and then I create a ftp user for that account.

And use ftp from there if I need a dB then I connect into cpanel and go to phpmyadmin.

On my other server I simply open WinScP using the Admin password for the WHM setup and then all the website accounts are there at a glance.

Then after this I go to the domain and simply change the name servers to that of WHM and all done.

So my question is now how to go about setting up a VPS so I can use my houndreds of domains.

I think let's start by the basics the we take it step by step.

First step what OS do I need.

Centos 6/7
Ubuntu
Debian
Arch

Please say why you suggest a certain one I would like to learn in the process and not do a monkey see monkey do approach I would like to understand.

 

[Hamster]

Ubuntu - because it is the easiest of them all.

Google: "site:digitalocean.com [question]"

"site:digitalocean.com initial server setup"
"site:digitalocean.com nginx multiple domains"
"site:digitalocean.com ftp users"
"site:digitalocean.com linux dash"

...or some other site. I say digitalocean because their guides are pretty damn easy.

TL;DR;

Google bro

 

[Thor]

Ubuntu - because it is the easiest of them all.

But is it the best?

 

[DrJohnZoidberg]

Take a look at ISPConfig too. It's pretty easy to manage and free.

 

[Thor]

That is what I used to use before I had money for cpanel.

I want to move into cli

Fck a GUI must become my motto

 

[gfmalan]

We use FreeBSD, and scripts to-do tasks, no GUI near this setup
Debian my favorite

 

[Thor]

Okey I am now looking at Debian, Ubuntu or Arch

From what I read it appears Ubuntu would be the better choice between it and it's cousin Debian because to my understanding debian has over 29,000 actively maintained packages available for download from the apt repositories, and the package maintainers prefer stability over “latest release” software which may have bugs and could compromise the stability of the Debian server thus running debian will ensure I have a stable OS however I might not have the latest technologies at my disposal and I will then have to use third party apt repositories, such as from the developer themselves or from third party repositories like DotDeb. I assume this is generally why Debian users move from Debian over to Ubuntu because if I understand it correctly debian works on ubuntu as well.

So now it is between ubuntu and Arch, Arch I read and read and to be honest I am fcking lost, but it appears Arch is a "rolling release", bleeding edge distro? The only way I can guarantee uptime would be to have a duplicate dev box, update/test there then push packages over? It seems to difficult/unnecessary compared to something like Ubuntu 14.04

This is the VPS -> VM-2

2 Core Processors
2GB Memory
40GB SSD Disk
200GB Traffic​

So before I proceed.
Is ubuntu 14.04 correct?

 

[gfmalan]

Ubuntu is based on Debian
http://www.ubuntu.com/about/about-ubuntu/ubuntu-and-debian

Why 14.04 LTS? 16.04 LTS is out, or do you prefer not to have the latest, and rather have the more supported version?!

 

[Thor]

Ubuntu is based on Debian
http://www.ubuntu.com/about/about-ubuntu/ubuntu-and-debian

Why 14.04 LTS? 16.04 LTS is out, or do you prefer not to have the latest, and rather have the more supported version?!

Ubtuntu is based on debian yes. However debian is not current. On ubuntu the software and repositories are updated, cutting edge. This does bring a disadvantage in that it can compromise stability if a package is not thoroughly tested by package maintainers or the developer of the package themselves.

As for 14.04 vs 16.04

This is the options I have:



Also my tutorial is 14.04
https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-14-04

 

[rward]

Thor,
stop asking "Is it the best, is it faster, is it number 1" and start doing.

You're going to mess up the install or config a couple of times, you're going to repeat this more than once so just dive in and do it.

Go with Ubuntu becasue it is the easiest and probably most supported (community).
Get that installed, get nginx installled, copy all the commands you run so you can easily copy and paste them when you do this the second time.

Read this:

Ubuntu - because it is the easiest of them all.

Google: "site:digitalocean.com [question]"

"site:digitalocean.com initial server setup"
"site:digitalocean.com nginx multiple domains"
"site:digitalocean.com ftp users"
"site:digitalocean.com linux dash"

...or some other site. I say digitalocean because their guides are pretty damn easy.

TL;DR;

Google bro

and follow what you find.

Seriously - it takes 2 minutes to spin up a new, clean instance so it doesn't matter if you don't get it 100% just right the first time.
Really, it doesn't, and you'll learn more getting it wrong!

 

[koeksGHT]

Ubuntu and Sentora for "WHM" otherwise terminal

 

[Thor]

Thor,
stop asking "Is it the best, is it faster, is it number 1" and start doing.

You're going to mess up the install or config a couple of times, you're going to repeat this more than once so just dive in and do it.

Go with Ubuntu becasue it is the easiest and probably most supported (community).
Get that installed, get nginx installled, copy all the commands you run so you can easily copy and paste them when you do this the second time.

Read this:



and follow what you find.

Seriously - it takes 2 minutes to spin up a new, clean instance so it doesn't matter if you don't get it 100% just right the first time.
Really, it doesn't, and you'll learn more getting it wrong!

Okey! I will do it right now!

Side note when does 16.04.1 get released since I would install 14.04 now and then would like to upgrade to 16

Can that be done?

 

[vinodh]

Okey! I will do it right now!

Side note when does 16.04.1 get released since I would install 14.04 now and then would like to upgrade to 16

Can that be done?

Ubuntu 16.04.1 LTS has already been released: http://fridge.ubuntu.com/2016/07/21/ubuntu-16-04-1-lts-released/

 

[Thor]

Ubuntu 16.04.1 LTS has already been released: http://fridge.ubuntu.com/2016/07/21/ubuntu-16-04-1-lts-released/

perfect!

 

[Thor]

Buying the VPS now.

One moment

 

[Thor]

Sorry was a bit busy.

Right VPS is here, I am putty'ed in.

I want to upgrade to 16.04 any idea why this does not work?



https://help.ubuntu.com/lts/serverguide/installing-upgrading.html

 

[Thor]

Nevermind

$ sudo apt-get update && sudo apt-get dist-upgrade

http://www.tecmint.com/upgrade-ubuntu-14-04-to-16-04/

 

[Thor]

This is why I hate these things. I do it by the books then ubuntu doesn't comply Why, then, is do-release-upgrade (without the -d) still saying "No new release found" a few days after the .1 has been released in iso form? (My /etc/update-manager/release-upgrades says "Prompt=lts")

From an inspection of the code, it seems that "normal" releases default to a URL changelogs.ubuntu.com/meta-release which lists 16.04, and LTS releases use the URL changelogs.ubuntu.com/meta-release-lts which doesn't list it at all. I think they haven't updated the meta information yet.

Fck me.

 

[Thor]

cool
View attachment 377702

 

[Johnatan56]

Nevermind

$ sudo apt-get update && sudo apt-get dist-upgrade

http://www.tecmint.com/upgrade-ubuntu-14-04-to-16-04/

First thing I do every time a command fails is check if I wrote sudo