Open drnickyoung opened 6 years ago
what messages did the vagrant provision show? Start again and watch what happens when it's provisioning. You can see the provision.sh script to find out what its doing.
Hi Tim,
Thanks for the reply. Just cleared it all out, delete old VB files and started fresh. Do Vagrant up and the only error I can spot is at the end:
==> default: Fetching git://github.com/timwaters/actionpack-action_caching.git
==> default: Fetching git://github.com/rails-api/active_model_serializers.git
==> default:
==> default: [!] There was an error while loading `active_model_serializers.gemspec`: can't modify frozen String. Bundler cannot continue.
==> default:
==> default: # from /home/vagrant/.bundle/ruby/1.9.1/active_model_serializers-0c552614a84f/active_model_serializers.gemspec:8
==> default: # -------------------------------------------
==> default: # spec.name = 'active_model_serializers'
==> default: > spec.version = ActiveModel::Serializer::VERSION
==> default: # spec.platform = Gem::Platform::RUBY
==> default: # -------------------------------------------
==> default: CREATE EXTENSION
==> default: now migrating database. This may take a few minutes
==> default: bundler: command not found: rake
==> default: Install missing gem executables with `bundle install`
==> default: /home/vagrant
As no one else seems to be getting/reporting an issue I assume this is me doing something totally stupid.
Nick
Hello,
it looks to be caused by old ruby version, overall.
After updating the gem
command with sudo REALLY_GEM_UPDATE_SYSTEM=true gem update --system
, the error of can't modify frozen String
is fixed and bundle install
says:
Bundler could not find compatible versions for gem "ruby":
In Gemfile:
ruby
active_model_serializers was resolved to 0.10.5, which depends on
case_transform (>= 0.2) was resolved to 0.2, which depends on
ruby (>= 2.0)
The default ruby on the VM is 1.9.3p484
.
Hi,
I did have this working by manualling install everything but after having been playing with it for a year thought I would go for a fresh install. I thought I would save time and spin up the Vagrant file only for it also not to work. So I do:
And with last command I get:
So I do:
And more and more errors follow. So question is am I doing something wrong or is there an issue with the vagrant file?
Nick