#bundle install

[root@localhost ]# bundle install Don’t run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Using blankslate 2.1.2.4 Using hitimes 1.2.2 Using timers 4.0.1 Using celluloid 0.16.0 Using fast-stemmer 1.0.2 Using classifier-reborn 2.0.3 Using coffee-script-source 1.9.1 Using execjs 2.3.0 Using coffee-script 2.3.0 Using colorator 0.1 Using ffi 1.9.6 Using jekyll-coffeescript 1.0.1 Using jekyll-gist 1.1.0 Using jekyll-paginate 1.1.0 Using sass 3.4.13 Using jekyll-sass-converter 1.3.0 Using rb-fsevent 0.9.4 Using rb-inotify 0.9.5 Using listen 2.8.5 Using jekyll-watch 1.2.1 Using kramdown 1.6.0 Using liquid 2.6.2 Using mercenary 0.3.5 Using posix-spawn 0.3.10 Using yajl-ruby 1.2.1 Using pygments.rb 0.6.2 Using redcarpet 3.2.2 Using safe_yaml 1.0.4 Using parslet 1.5.0 Using toml 0.1.2 Using jekyll 2.5.3 Using jekyll-sitemap 0.8.0 Using octopress-deploy 1.1.0 Using octopress-hooks 2.6.0 Using octopress-escape-code 2.0.6 Using titlecase 0.1.1 Using octopress 3.0.0.rc.34 Using bundler 1.10.6 Bundle complete! 4 Gemfile dependencies, 38 gems now installed. Use `bundle show [gemname]` to see where a bundled gem is installed.

If you're trying to connect to the local server and 'foreman start' doesn't work, because you get an error that contains (Bundler :: Gem Not Found).

try typing

bundle install [enter]

then letting all the ruby gems install that you may be missing

then try again:

foreman start [enter]

It would be great if we were notified when to run bundle install and/or migrate the database!

We are going to use the post-merge git hook, which is called after you pull from the repository.

In the root of your project directory, cd to .git/hooks.

$ touch post-merge <-- create the post-merge hook file

$ chmod +x post-merge <-- this makes the file executable

Open the post-merge file you just created (ex: $ sublime post-merge OR $ vi post-merge)

A common ill when running rails for the first time is that the sqlite3 gem won't install, this is generally has to do with the sqlite gem being a "C gem" not a "ruby gem" and hence needing all sorts of build enviroment tools.

The solution is fairly simple, you just need to install the ruby-dev and libsqlite3-dev packages. The problem is that #! has dependency issues with the libsqlite3-dev package.

The following packages have unmet dependencies: libsqlite3-dev : Depends: libsqlite3-0 (= 3.7.3-1) but 3.7.12.1-1~bpo60+1 is to be installed

To resolve the issue you need to go into your synaptic package manager and find the offending package and use the Package > Force Version to force the version to a stable version.