-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git, bundle, rvm, rails, etc does not work out of the box? #7
Comments
This repo is not maintained at the moment, I haven't used it in a long time and probably nothing works with current versions. You might want to have a look at https://gorails.com/guides/using-vagrant-for-rails-development or http://tutorials.jumpstartlab.com/topics/vagrant_setup.html |
I'll send you a pull request if I ever end up figuring out how to fix your provisioning, which I want to do just out of curiosity. In the meantime, I've been using a pre-configured box directly from Vagrant's site for Rails. That gorails link is great, and I've tried it previously a couple months back, but had the similar result of the end result not working. Thanks for the reply! |
Could you please add the fact that it is not maintained to the readme, thanks. |
@voronoipotato just merged you pull request updating the readme to say that the project is not maintained, thanks! |
I'm a bit inexperienced with vagrant so perhaps I am doing something wrong. I cloned the rails-starter-box repo and followed all the README instruction. When I 'vagrant ssh' into the box after 'vagrant up', the programs that are supposed to be in the box already are not, such as git, rvm, rails, bundle, etc. Using these commands result in the following (in the example of git):
"The program 'git' is currently not installed. You can install it by typing sudo apt-get install git"
Yet, I'm able to fully interact with the box otherwise, such as install packages, manipulate and navigate directories, etc.
Is there some fundamental step I'm missing that is not in the README?
The text was updated successfully, but these errors were encountered: