Skip to content

Instantly share code, notes, and snippets.

@craftninja
Last active August 29, 2015 14:08
Show Gist options
  • Save craftninja/54c75a7ee47a4d1542a9 to your computer and use it in GitHub Desktop.
Save craftninja/54c75a7ee47a4d1542a9 to your computer and use it in GitHub Desktop.
Coderwall setup

getting coderwall up and running

  1. fork https://github.com/assemblymade/coderwall

  2. clone your project

  3. download VirtualBox 4.3.12 and associated extension pack from https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

  4. download Vagrant 1.6.5 from http://www.vagrantup.com/downloads.html

  5. install Virtual Box

  6. install associated extension pack

  7. install vagrant

  8. install vagrant plugins (in terminal)

    $ vagrant plugin install vagrant-vbguest
    $ vagrant plugin install vagrant-cachier
    
  9. cd into project directory

  10. had to update ruby

    $ rvm install ruby-2.1.4
    
  11. updated RVM

    $ rvm get stable
    
  12. add upstream remote to local project

    $ git add remote upstream git@github.com:assemblymade/coderwall.git
    
  13. copy vagrant.yml.example to vagrant.yml

  14. within the project directory

  • this takes a while... more than an hour?

    $ ./run.sh
    
  • once you see something like:

    $ 18:04:25 web.1     | [3546] * Listening on tcp://0.0.0.0:3000
    $ 18:04:25 web.1     | [3546] Use Ctrl-C to stop
    
  1. open another terminal tab

    $ vagrant ssh
    $ pwd
    $ hostname
    $ ls -al
    
  2. now we can run the app??... but app is already running in first tab! in the same terminal tab, still ssh'ed into vagrant (run first command just above):

    $ cd ~/web
    $ rvm current
    => ruby-2.1.4@coderwall for me
    $ bundle check
    => The Gemfile's dependencies are satisfied
    $ rails s
    => #bunch of stuff#
    => Address already in use - bind(2) for 0.0.0.0:3000 (Errno::EADDRINUSE)
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment