g5 / g5-orion-vagrant Goto Github PK

If we use the base box from G5/g5stack, we can remove almost all of the Chef code from this project, and we will automatically get any common updates (e.g. upgrading Ubuntu). We can replace the git submodules with berkshelf.

The current build scripts set up multiple environment variables that probably aren't necessary, including HEROKU_APP_NAME. Setting this particular env var causes issues with the g5-hub test suite. It doesn't make much sense to export this variable globally in a development environment that hosts multiple apps, each of which uses dotenv to manage its own development environment.

You gotta get the repo before you can setup, yeah?

$ vagrant up
$ vagrant ssh
$ cd /g5-content-management-system

Needed to sudo apt-get install rails before bundle exec rails server

Also note that rails server resulted in a "undefined method `write_inheritable_attribute' for Rails::Generator::Base:Class" error. Adding bundle exec to the command fixed this. We may want to add that to the README.

Hey @jlsuttles, I was getting some test failures that ended up being some test gems not being required automatically by bundler as usual. I unset the RAILS_ENV variable (which you added recently) and the gem became available as expected.

The only place I've seen a real environment variable set like that is on production servers, where you don't expect to run multiple environments. Unless there was a reason I'm missing, I think we should revert that commit.