tomcbe

You can have finer control with:

rake db:drop:all

And then create the database without running the migrations:

rake db:create:all

Then run all your migrations:

tomcbe

### Add trailing slash if needed

STR="/i/am/a/path"

length=${#STR}
last_char=${STR:length-1:1}

[[ $last_char != "/" ]] && STR="$STR/"; :

echo "$STR" # => /i/am/a/path/

tomcbe

Find out what package installed the config file:

$ dpkg -S unity-greeter.conf
unity-greeter: /etc/lightdm/unity-greeter.conf

As you can see, the name of the package is unity-greeter.

If you deleted a directory, like /etc/pam.d, you can list every package that added to it by using the directory path:

tomcbe

Update 7/28/2019: An updated version of this guide for Ubuntu Server 18.04 LTS is now available. Feel free to check it out.

Mounting VirtualBox shared folders on Ubuntu Server 16.04 LTS

This guide will walk you through steps on how to setup a VirtualBox shared folder inside your Ubuntu Server guest. Tested on Ubuntu Server 16.04.3 LTS (Xenial Xerus)

Steps:

1. Open VirtualBox
2. Right-click your VM, then click Settings
3. Go to Shared Folders section

tomcbe

openssl

Install

Install the OpenSSL on Debian based systems

sudo apt-get install openssl

tomcbe

# username
# appname
# gemset

[Unit]
Description=Puma HTTP Server
After=network.target

[Service]
Type=forking

tomcbe

[Unit]
Description=Puma HTTP Server
After=network.target

# Uncomment for socket activation (see below)
# Requires=puma.socket

[Service]
# Foreground process (do not use --daemon in ExecStart or config.rb)
Type=simple

tomcbe

wget -P/local/target/directory -r -nH -np --reject html http://mirrors.dotsrc.org/maven2/ 
wget will put a maven2 repository folder under /local/target/directory on your machine, along with all the repositories artifacts.

tomcbe

Safest way to clean up boot partition - Ubuntu 14.04LTS-x64, Ubuntu 16.04LTS-x64

Reference

Case I: if /boot is not 100% full and apt is working

1. Check the current kernel version

$ uname -r 

tomcbe

You don't have to delete your local branch.

Simply delete your remote tracking branch:

git branch -d -r origin/<remote branch name> (This will not delete the branch on the remote repo!)

See "Having a hard time understanding git-fetch"

there's no such concept of local tracking branches, only remote tracking branches.