apt-get remove apache2 apache2-bin apache2-data apache2-doc apache2-mpm-prefork apache2-utils

For CentOS:

yum remove httpd httpd-tools

Once you removed all the Apache related packages, you can actually proceed with GitLab. First you will need to install some repositories, which will be used to download and install GitLab.

For Debian/Ubuntu:

curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash

For CentOS:

curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash

After you add the required repositories, you can proceed with installation:

For Debian/Ubuntu:

sudo EXTERNAL_URL="http://your.subdomain.com" apt-get install gitlab-ee

For CentOS:

sudo EXTERNAL_URL="http://your.subdomain.com" yum -y install gitlab-ee

Note. Change "http://your.subdomain.com" with your domain/subdomain, which will be used to open GitLab.

The installation may take up to 5-7 minutes, but once it is done, you will be present with some huge image on your terminal about completion. After that you will have to go to your chosen URL (for example: http://your.subdomain.com) and change the password.

The default username will be root, so you can log in to GitLab with this username and your newly changed password.

Note. If you install the GitLab, without removing Apache first, you may need to configure virtual host, as you will most likely be displayed with default Apache webpage, when trying to connect to your chosen URL.

More information on official site: https://about.gitlab.com/

apt-get update

apt-get install -y apt-transport-https

apt install docker.io -y

systemctl start docker && systemctl enable docker

2. Installation Of Kubernetes:

curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add 

nano /etc/apt/sources.list.d/kubernetes.list

deb http://apt.kubernetes.io/ kubernetes-xenial main

apt-get update && apt-get install -y kubelet kubeadm kubectl kubernetes-cni

sudo kubeadm init

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

kubeadm join <master node IP>:6443 --token i5s534.38o26swycl0gd0gr --discovery-token-ca-cert-hash sha256:4b4c8d9652e925dffe0f28c73984c27d821cd998f63525dd45378a762517dea3
 

kubeadm token generate

kubeadm join <master node IP>:6443 --token 
i5s534.38o26swycl0gd0gr --discovery-token-ca-cert-hash 
sha256:4b4c8d9652e925dffe0f28c73984c27d821cd998f63525dd45378a762517dea3

kubectl get nodes

Command results should look similar to:

NAME                     STATUS    ROLES     AGE       VERSION
Node.hostname   Ready     <none>    1d        v1.11.2
Master.hostname   Ready     master    1d        v1.11.2
...

You can now set services for you cluster or scale it's size by adding additional servers to the cluster in the same way as you have added the first node. For more information on cluster management, loads of useful information is provided in the Kubernetes Documentation. Good luck with your cluster!

Introduction

By default on Ubuntu the Apache2 web server stores its files in "/var/www/html" folder. Sometimes it’s helpful to move it to another location, such as a separate mounted file system and so on.

In this tutorial you will learn how to move the default directory to a new location. We are using Ubuntu 16.04 for this tutorial, however you should be able to follow this guide using any of our offered Ubuntu or Debian distributions.


Copying Files

We are using "rsync" for coping files to a new location:

rsync -av /var/www/html /new/location

Where "-a" flag preserves the permissions and other directory properties and "-v" flag provides comprehensive output.

Note: If you are using "Tab" completion be sure to delete trailing slash "/" on the the directory.


Updating The Configuration File

Now we need to update "000-default.conf" file:

nano /etc/apache2/sites-enabled/000-default.conf

Now we will find the line that begins with "DocumentRoot" and update it with the new location. It should look something like this:


# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

ServerAdmin webmaster@localhost
DocumentRoot /nauja/direktorija

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf


# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


Restarting Apache

Once you’ve finished the configuration changes, you can make sure the syntax is right with "configtest":

apachectl configtest

If everything is right you should get result:

Syntax OK

As long as you get Syntax OK, restart the web server. Otherwise, track down and fix the problems it reported. Use the following command to restart Apache:

systemctl reload apache2


Conclusion

That's it! You changed Apache's default folder and from know all your affected sites will be loaded from new location.

Introduction

Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.

Nearly every popular CMS has a plugin or module to take advantage of memcached, and many programming languages have a memcached library, including PHP, Perl, Ruby, and Python. Memcached runs in memory and is thus quite speedy, since it does not need to write data to disk.


Installation

We can install Memcached by running this command:

apt-get install memcached -y


Configuration

Use the following command to edit the default configuration file /etc/memcached.conf:

nano /etc/memcached.conf

You will see default configurations of memcached, such as default port (11211), cap of memory for memcached in megabytes (64) and so on.

Most common variables to edit:

p - port in which memcached is running
m - cap of memory for memcached
c - value of maximum connections

An example how should look configuration file if we want memcached to run on port 12345, to use 2 GB of RAM and have 1024 allowed maximum connections:

# memcached default config file
# 2003 - Jay Bonci
# This configuration file is read by the start-memcached script provided as
# part of the Debian GNU/Linux distribution.

# Run memcached as a daemon. This command is implied, and is not needed for the
# daemon to run. See the README.Debian that comes with this package for more
# information.
-d

# Log memcached's output to /var/log/memcached
logfile /var/log/memcached.log

# Be verbose
# -v

# Be even more verbose (print client commands as well)
# -vv

# Start with a cap of 64 megs of memory. It's reasonable, and the daemon default
# Note that the daemon will grow to this size, but does not start out holding this much
# memory
-m 2048

# Default connection port is 11211
-p 11211

# Run the daemon as root. The start-memcached will default to running as root if no
# -u command is present in this config file
-u memcache

# Specify which IP address to listen on. The default is to listen on all IP addresses
# This parameter is one of the only security measures that memcached has, so make sure
# it's listening on a firewalled interface.
-l 127.0.0.1

# Limit the number of simultaneous incoming connections. The daemon default is 1024
-c 1024

# Lock down all paged memory. Consult with the README and homepage before you do this
# -k

# Return error when memory is exhausted (rather than removing items)
# -M

# Maximize core file limit
# -r


Finalizing

After we had configured mamached to work with parameters we want we can start it:

service memcached start

We can test is it working with commands

service memcached status

or

pgrep memcached
netstat -tulpn | grep :11211

Conclusion

That's it! You had installed and configured basics of memcached. So, now you have very useful program which can do a lot to increase the server efficiency.

As always, before making any changes to your VPS, you should make a backup of your VPS - save all the essential data. It will be a wise option if anything goes wrong.

Steps:

1. First of all, you need to update all the system packages and repositories:

sudo yum update -y

2. Then you need to reboot your VPS:

sudo reboot

You might be disconnected from your VPS, so you will need to connect to your VPS again.

3. After that, you need to install the elevate-release package with this command:

sudo yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el7.noarch.rpm

After the installation is completed, the output should look something like this:

4. The next step is to install leapp-data-almalinux package:

sudo yum install -y leapp-upgrade leapp-data-almalinux

5. Then, you need to initiate a pre-upgrade check. Down below provided command runs the checks to see if the upgrade will be successful or not and provides a report of possible remediations:

sudo leapp preupgrade

If due to some reason the test fails, all the reasons will be saved in a file that path is /var/log/leapp/answerfile.

6. If pre-upgrade is successful, you will need to run these commands:

sudo rmmod pata_acpi

echo PermitRootLogin yes | sudo tee -a /etc/ssh/sshd_config

sudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True

7. Now, you can run the following command to migrate your OS from CentOS 7 to AlmaLinux:

sudo leapp upgrade

It might take up some time, so be patient.

Then reboot your VPS again:

sudo reboot

It might take up to 20-30 minutes; meanwhile, the server will not be accessible via SSH. Do not worry, you can try to access your VPS via Emergency Console and watch how the files are installing.

When the installation is completed, you will be asked to log in. So then you can try to connect to your VPS as root.

Once you log in to your VPS, you can run this command to check your OS version:

cat /etc/redhat-release

If AlmaLiux was installed, you should see a similar output:

And that's it, you have upgraded your OS successfully to AlmaLinux!

Introduction

Node.js is a Javascript platform for server-side programming that allows users to build network applications quickly. By leveraging Javascript on both the front-end and the back-end, development can be more consistent and be designed within the same system.

For as popular as this JavaScript run-time has become, you might be surprised to find out that it actually still isn't very easy to install Node.js on Ubuntu and other Linux distributions. It's still more of a manual process than it should be.

In this guide, we'll show you 3 ways how to get started with Node.js on an Ubuntu/Debian server.

Note: Tutorial on how to set up a Node.js application for production is on the way and will be released in few weeks.


1. Distro-Stable Version

Ubuntu/Debian contains a version of Node.js in its default repositories that can be used to easily provide a consistent experience across multiple servers. Usually it will not be the latest version, but it should be quite stable.

In order to get this version, we just have to use the apt package manager:

sudo apt-get install nodejs

If the package in the repositories suits your needs, this is all that you need to do to get set up with Node.js. In most cases, you'll also want to also install npm, which is the Node.js package manager. You can do this by typing:

sudo apt-get install npm

This will allow you to easily install modules and packages to use with Node.js.


2. PPA (Personal Package Archive)

An alternative that can get you a more recent version of Node.js is to add a PPA maintained by NodeSource. This will probably have more up-to-date versions of Node.js than the official Ubuntu repositories.

First, you need to install the PPA in order to get access to its contents.

curl -sL https://deb.nodesource.com/setup | sudo bash -

Note: If you got error "-bash: curl: command not found" it means you do not have curl installed on your server. You can install it with command:

sudo apt-get install curl -y

The PPA will be added to your configuration and your local package cache will be updated automatically. After running the setup script from nodesource, you can install the Node.js package in the same way that you did above:

sudo apt-get install nodejs


3. NVM (Node.js Version Manager)

Using NVM, you can install multiple, self-contained versions of Node.js which will allow you to control your environment easier. It will give you on-demand access to the newest versions of Node.js, but will also allow you to target previous releases that your app may depend on.

First of all we need to get the software packaged from Ubuntu/Debian repositories:

sudo apt-get install build-essential libssl-dev

Once the prerequisite packages are installed, you can pull down the NVM installation script from the project's GitHub page:

https://github.com/creationix/nvm

Execute command:

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.1/install.sh | bash

This will download the script and run it. It will install the software into a subdirectory of your home directory at /.nvm. It will also add the necessary lines to your /.profile file to use the file.

To gain access to the nvm functionality, you'll need to log out and log back in again, or you can source the /.profile file so that your current session knows about the changes:

source ~/.profile

Now that you have nvm installed, you can install isolated Node.js versions.

To find out the versions of Node.js that are available for installation, you can type:

nvm ls-remote

As you can see, the newest version at the time of this writing is v6.2.0. You can install that by typing:

nvm install 6.2.0

Usually, nvm will switch to use the most recently installed version. You can explicitly tell nvm to use the version we just downloaded by typing:

nvm use 6.2.0

When you install Node.js using nvm, the executable is called node. You can see the version currently being used by the shell by typing:

node -v


Conclusion

And that's it, you're done! Regardless of whatever installation method you used, you should run node -v to verify the build/install worked correctly.

rpm -Uvh http://mirror.overthewire.com.au/pub/epel/6/i386/epel-release-6-8.noarch.rpm

For CentOS 6 64-bit execute command:

rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

Install required packages:

yum install clamav clamd

Start the clamd service and set it to auto-start

/etc/init.d/clamd on
chkconfig clamd on
/etc/init.d/clamd start

Update ClamAV's signatures:

/usr/bin/freshclam

Note: ClamAV will update automatically, as part of /etc/cron.daily/freshclam.

Configure daily scan

In this example, we will configure a cronjob to scan the /var/www directory every day. Create cron file:

nano /etc/cron.daily/man_clamscan

Add the following to the file above. Be sure to change SCAN_DIR to the directory that you want to scan:

#!/bin/bash
SCAN_DIR="/var/www"
LOG_FILE="/var/log/clamav/man_clamscan.log"
/usr/bin/clamscan -i -r $SCAN_DIR >> $LOG_FILE

Give our cron script executable permissions:

chmod +x /etc/cron.daily/man_clamscan

That's it.

Install OpenVPN:

For CentOS:

rpm -ivh openvpn-[details].rpm

For Debian:

dpkg -i DEB_PACKAGE

That's it! Read post install message in SSH for login details / instructions.

Requirements for using SSH to login to your VPS or Dedicated Server

There are a few requirements for using SSH with your VPS or Dedicated Server. These include making sure that your account has been granted SSH access and that your IP address has been added to the firewall. Both of these requirements can be fulfilled through the WHM interface. The following articles will help you meet these prerequisites:

1. Configure SSH access
2. Whitelist your IP address in your server firewall
3. Windows users, install an SSH Client or OpenSSH

Terminal on Linux/macOS/BSD

This applies to Windows users with OpenSSH: Open the Start menu,select Powershell, and then Run as Administrator.

If you are trying to directly connect from a Linux or Mac terminal via SSH, please note the format of the command would need to be in this format:18If you are trying to directly connect from a Linux or Mac terminal via SSH, please note the format of the command would need to be in this format:

[Bob ~]$ ssh username@example.com -p 22

If you do not specify the full username such as username@example, the server would instead try to login as your local user, in this case Bob@example.com, and because that user doesn’t exist on the server you’d get a login error.