Set up Virtual Development Environment with Vagrant

[DBNess]

Ask
Set up automated CodeMontage environment using Vagrant & include setup instructions in README.

To Do

• Set up CodeMontage environment in Vagrant
• Add Vagrant setup instructions to README

Additional Info
Related to #254 & #277.

[DBNess]

Possible resources:
https://github.com/ponticlaro/vagrant-heroku-template
https://github.com/ejholmes/vagrant-heroku
http://loudcoding.com/posts/how-to-use-vagrant-to-run-celadon-cedar-stack-on-heroku

Also asked Heroku for their recommendation via Twitter: https://twitter.com/DBNess/status/441249130976124928

[jake-bladt]

I'd like to take a look at this one. I'm already kicking around virtualization solutions for Ruby at home.

[DBNess]

@jake-bladt awesome! I'm hoping we can get a template as close to Heroku as possible, but if not a general Ubuntu + Postgres setup should do the trick. I've got Vagrant and VirtualBox set up already so should be able to test this in a timely manner if you get the chance to try something out

[steverob]

This is a great idea! 👍

[jake-bladt]

@DBNess, @steverob - progress can be tracked in https://github.com/jake-bladt/codemontage/tree/support_vagrant

[DBNess]

Sweet! thanks, @jake-bladt (also in case this view helps anyone else: https://github.com/jake-bladt/codemontage/compare/support_vagrant)

[jake-bladt]

I have this nearly working now, but bundle install is failing on the VM because of psych - something similar to this issue reported on the actual cedar stack: localeapp/localeapp#27. Will investigate that next.

[jake-bladt]

I was able to fix the lack of libyaml-dev by manually installing it on the vagrant VM manually after vagrant up. I'm working on a fork of vagrant-heroku, but somehow my changes still didn't get the properly library installed.

This workaround did solve the problem of being unable to build psych on the VM. Now I've got a new problem. When I run rails and navigate to the site in my browser, I get the following:

Errno::ETXTBSY in Home#index

Showing /vagrant/app/views/layouts/application.html.erb where line #25 raised:

Text file busy - (/vagrant/tmp/cache/sass/9505375e72afa48c5767235c7d79f01d960d4322/application.scssc20140315-1005-uenw2e, /vagrant/tmp/cache/sass/9505375e72afa48c5767235c7d79f01d960d4322/application.scssc)
(in /vagrant/app/assets/stylesheets/application.scss)
Extracted source (around line #25):

22: <title><%= content_for?(:title) ? yield(:title) : "CodeMontage" %></title>
23:
24:
25: <%= stylesheet_link_tag "application" %>
26:
27:
28: <%= javascript_include_tag "vendor/custom.modernizr" %>

I'm trying to address this by running rake assets:precompile before starting the rails server and will report back when I have more information.

[jake-bladt]

Update: This may be the problem:
http://stackoverflow.com/questions/19124367/rails-app-on-percise32-vagrant-box-assets-get-text-file-busy-error-errnoe

[DBNess]

I've been working on this repeatedly, in pieces, for months, but keep running into issues either on the Vagrant box itself or when I deploy the branch to Heroku -- now hoping to use Codio instead and minimize all of the changes (hopefully!) with #254.