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:
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:
| ### 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/ |
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:
| # username | |
| # appname | |
| # gemset | |
| [Unit] | |
| Description=Puma HTTP Server | |
| After=network.target | |
| [Service] | |
| Type=forking |
| [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 |
| 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. |
$ uname -r
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.