jstribny's profile - activity

NFS has to be running (started) on guest. There was in issue in Vagrant source code so that did not happened for Fedora guests. If you used Fedora guests, perhaps this was the issue. It's fixed in latest bug release:

sudo dnf update vagrant --enablerepo=updates-testing

What about using some plugin for that like https://github.com/tmatilai/vagrant-p...

This might depend on your boxes. If you use Fedora boxes than there was a bug that I fixed and I also made fixed vagrant builds for Fedora 22 and 21. There are still in updates-testing so try to update Vagrant as:

sudo dnf update vagrant --enablerepo=updates-testing

Hope it helps.

This won't work in Fedora 13...

Yes. This is because of Fedora packaging policy does not allow bundling (apart from the exceptions). But you don't need to package tzinfo-data, because tzinfo works now with system tzdata database.

Would you post exact steps you did and minimal Vagrantfile you have?

You need header files for compiling C extensions of the gems, but the ones in the Rails stack are packaged and therefore you don't need them unless you need to install new gems from the internet.

Rails packager here. We do package all dependencies, but Bundler will still try to fetch the newest ones. The solution is to skip the bundle by running rails new app --skip-bundle. You can then create a Gemfile.lock file with bundle --local. That will succeed only if you install the other packages as well:

dnf install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,therubyracer,sdoc,spring,byebug,web-console}

If you need a newer version of any component, you need to lock the packaged versions yourself and then you can run bundle command as normal. Also note that on Fedora 22 dnf sometimes installs JRuby instead of MRI. Unfortunately JRuby is not ready yet to be used on Fedora so in that case install ruby package yourself.