FAQ Overview

Ubuntu 14.04.5 LTS

What is the Apache Restart Command

service apache2 restart

Author: Ed Casillas
Last update: 2018-06-18 03:21

Let's Encrypt Commad to Add Domain Name

--> certbot --apache -d example.com -d www.example.com

Author: Ed Casillas
Last update: 2018-06-18 19:45

How To Set Up Apache Virtual Hosts

Step One — Create the Directory Structure

The first step that we are going to take is to make a directory structure that will hold the site data that we will be serving to visitors.

Our document root (the top-level directory that Apache looks at to find content to serve) will be set to individual directories under the /var/www directory. We will create a directory here for both of the virtual hosts we plan on making.

Within each of these directories, we will create a public_html folder that will hold our actual files. This gives us some flexibility in our hosting.

For instance, for our sites, we're going to make our directories like this:

sudo mkdir -p /var/www/example.com/public_html
sudo mkdir -p /var/www/test.com/public_html

The portions in red represent the domain names that we are wanting to serve from our VPS.

Step Two — Grant Permissions

Now we have the directory structure for our files, but they are owned by our root user. If we want our regular user to be able to modify files in our web directories, we can change the ownership by doing this:

sudo chown -R $USER:$USER /var/www/example.com/public_html
sudo chown -R $USER:$USER /var/www/test.com/public_html

The $USER variable will take the value of the user you are currently logged in as when you press "ENTER". By doing this, our regular user now owns the public_html subdirectories where we will be storing our content.

We should also modify our permissions a little bit to ensure that read access is permitted to the general web directory and all of the files and folders it contains so that pages can be served correctly:

sudo chmod -R 755 /var/www

Your web server should now have the permissions it needs to serve content, and your user should be able to create content within the necessary folders.

Step Three — Create Demo Pages for Each Virtual Host

We have our directory structure in place. Let's create some content to serve.

We're just going for a demonstration, so our pages will be very simple. We're just going to make an index.html page for each site.

Let's start with example.com. We can open up an index.html file in our editor by typing:

nano /var/www/example.com/public_html/index.html

In this file, create a simple HTML document that indicates the site it is connected to. My file looks like this:

    <title>Welcome to Example.com!</title>
    <h1>Success!  The example.com virtual host is working!</h1>

Save and close the file when you are finished.

We can copy this file to use as the basis for our second site by typing:

cp /var/www/example.com/public_html/index.html /var/www/test.com/public_html/index.html

We can then open the file and modify the relevant pieces of information:

nano /var/www/test.com/public_html/index.html
    <title>Welcome to Test.com!</title>
    <h1>Success!  The test.com virtual host is working!</h1>

Save and close this file as well. You now have the pages necessary to test the virtual host configuration.

Step Four — Create New Virtual Host Files

Virtual host files are the files that specify the actual configuration of our virtual hosts and dictate how the Apache web server will respond to various domain requests.

Apache comes with a default virtual host file called 000-default.conf that we can use as a jumping off point. We are going to copy it over to create a virtual host file for each of our domains.

We will start with one domain, configure it, copy it for our second domain, and then make the few further adjustments needed. The default Ubuntu configuration requires that each virtual host file end in .conf.

Create the First Virtual Host File

Start by copying the file for the first domain:

sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/example.com.conf

Open the new file in your editor with root privileges:

sudo nano /etc/apache2/sites-available/example.com.conf

The file will look something like this (I've removed the comments here to make the file more approachable):

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

As you can see, there's not much here. We will customize the items here for our first domain and add some additional directives. This virtual host section matches any requests that are made on port 80, the default HTTP port.

First, we need to change the ServerAdmin directive to an email that the site administrator can receive emails through.

ServerAdmin admin@example.com

After this, we need to add two directives. The first, called ServerName, establishes the base domain that should match for this virtual host definition. This will most likely be your domain. The second, called ServerAlias, defines further names that should match as if they were the base name. This is useful for matching hosts you defined, like www:

ServerName example.com
ServerAlias www.example.com

The only other thing we need to change for a basic virtual host file is the location of the document root for this domain. We already created the directory we need, so we just need to alter the DocumentRoot directive to reflect the directory we created:

DocumentRoot /var/www/example.com/public_html

In total, our virtualhost file should look like this:

<VirtualHost *:80>
    ServerAdmin admin@example.com
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot /var/www/example.com/public_html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

Save and close the file.

Copy First Virtual Host and Customize for Second Domain

Now that we have our first virtual host file established, we can create our second one by copying that file and adjusting it as needed.

Start by copying it:

sudo cp /etc/apache2/sites-available/example.com.conf /etc/apache2/sites-available/test.com.conf

Open the new file with root privileges in your editor:

sudo nano /etc/apache2/sites-available/test.com.conf

You now need to modify all of the pieces of information to reference your second domain. When you are finished, it may look something like this:

<VirtualHost *:80>
    ServerAdmin admin@test.com
    ServerName test.com
    ServerAlias www.test.com
    DocumentRoot /var/www/test.com/public_html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

Save and close the file when you are finished.

Step Five — Enable the New Virtual Host Files

Now that we have created our virtual host files, we must enable them. Apache includes some tools that allow us to do this.

We can use the a2ensite tool to enable each of our sites like this:

sudo a2ensite example.com.conf
sudo a2ensite test.com.conf

When you are finished, you need to restart Apache to make these changes take effect:

sudo service apache2 restart

You will most likely receive a message saying something similar to:

 * Restarting web server apache2
 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using Set the 'ServerName' directive globally to suppress this message

This is a harmless message that does not affect our site.

Author: Ed Casillas
Last update: 2018-07-09 03:08

VIM Editor

VIM - How to set Line Number

Esc ":set number"

Author: Ed Casillas
Last update: 2018-06-18 20:14

VIM - How to automatically see Line Numbers when accessing vi

- Create .vimrc file 
- Add "set number" to the .vimrc file

Author: Ed Casillas
Last update: 2018-06-18 21:27

VIM - Common Commands

How to Exit

 :q[uit] Quit Vim. This fails when changes have been made.
 :q[uit]! Quit without writing.
 :cq[uit] Quit always, without writing.
 :wq Write the current file and exit.
 :wq! Write the current file and exit always.
 :wq {file} Write to {file}. Exit if not editing the last
 :wq! {file} Write to {file} and exit always.
 :[range]wq[!] [file] Same as above, but only write the lines in [range].
 ZZ Write current file, if modified, and exit.
 ZQ Quit current file and exit (same as ":q!").

Editing a File

 :e[dit] Edit the current file. This is useful to re-edit the current file, when it has been changed outside of Vim.
 :e[dit]! Edit the current file always. Discard any changes to the current buffer. This is useful if you want to start all over again.
 :e[dit] {file} Edit {file}.
 :e[dit]! {file} Edit {file} always. Discard any changes to the current buffer.
 gf Edit the file whose name is under or after the cursor. Mnemonic: "goto file".

Inserting Text

a Append text after the cursor [count] times.
A Append text at the end of the line [count] times.
i Insert text before the cursor [count] times.
I Insert text before the first non-blank in the line [count] times.
gI Insert text in column 1 [count] times.
o Begin a new line below the cursor and insert text, repeat [count] times.
O Begin a new line above the cursor and insert text, repeat [count] times.

Author: Ed Casillas
Last update: 2020-05-19 02:38

VIM - Search and Replace Commands

:s/foo/bar/g Change each 'foo' to 'bar' in the current line
:%s/foo/bar/g Change each 'foo' to 'bar' in all the lines
:5,12s/foo/bar/g Change each 'foo' to 'bar' for all lines from line 5 to line 12 (inclusive)
 :'a,'bs/foo/bar/g  Change each 'foo' to 'bar' for all lines from mark a to mark b inclusive (see Note below)
 :'s/foo/bar/g  When compiled with +visual, change each 'foo' to 'bar' for all lines within a visual selection. Vim automatically appends the visual selection range (') for any ex command when you select an area and enter :. Also, see Note below.
:.,$s/foo/bar/g Change each 'foo' to 'bar' for all lines from the current line (.) to the last line ($) inclusive
 :.,+2s/foo/bar/g  Change each 'foo' to 'bar' for the current line (.) and the two next lines (+2)
:g/^baz/s/foo/bar/g  Change each 'foo' to 'bar' in each line starting with 'baz'

Author: Ed Casillas
Last update: 2018-07-07 02:18

SSH Commands

How to copy a local directory or file to a remote machine or another remote machine

Local Directory to Remote Machine:
/path/to/local/dir usrname@hostname:/path/to/remote/dir

Remote Machine to Local Directory
scp username@hostname:/path/to/remote/file /path/to/local/file

Remote Machine to Remote Machine
scp username1@hostname1:/path/to/file username2@hostname2:/path/to/other/file

Author: Ed Casillas
Last update: 2018-10-20 19:26