You can follow the instructions on the Ansible website or either of the options below:
sudo easy_install pip
sudo pip install ansible
brew install ansible
sudo apt-get install python-yaml python-markupsafe nfs-kernel-server nfs-common portmap
sudo apt-get install software-properties-common
Test to see if ansible is installed using ansible --version If it is not installed, do the following:
sudo apt-add-repository ppa:ansible/ansible
sudo apt-get update
sudo apt-get install ansible
yum install ansible
Download VirtualBox and install.
Download Vagrant and install.
Go to directory you want clone into. For example, if you want to clone into /someuser/myapps/
You could do: cd /someuser/myapps/
Then type below:
git clone https://github.com/webapp-builders/groundwork.git
cd groundwork
You can confirm that you are in the correct directory by typing ls.
If you see a file Vagrantfile you are in the correct directory.
Note: If you are using ubuntu as your primary OS, uncomment line 22 to use the VirtualBox GUI.
Note: If your computer only supports 32-bit operating systems, after cd groundwork, open the file: Vagrantfile
Comment out line 3 and uncomment line 5 to use "ubuntu/trusty64"
(this will tell VirtualBox to run the "precise32" operating system).
vagrant up
READ Below for possible "terminal messages":
Numerous messages and errors may occur once typing vagrant up.
Read the following Terminal Message 1 and Terminal Message 2, to make sure you are on the right track.
Terminal Message 1: If your terminal seems to be "stuck" at TASK: rvm... just wait. This might take a while, because you are installing Ruby using RVM. This is a good sign. It means everything is installing properly.
Terminal Message 2: You many receive an error if you already have Rail or Postgresql running on your machine.
This means you need to stop Rails and/or Postgresql.
An error might look like the following:
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 5432 is already in use
on the host machine.
To fix this, modify your current projects Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:
config.vm.network :forwarded_port, guest: 5432, host: 1234
Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding.
For Rails server, find the terminal window that is running Rails locally and press ctrl+c together.
You may not realize it, but Postgres might have started automatically at startup.
If Postgresql is running, to stop your:
For Ubuntu:
sudo service postgresql stop
For OSX homebrew:
Go online, search for "how to stop postgresql osx"
(There will be different instructions depending on how your Mac is setup).
(You may skip this command for a first time install)
Upon subsequent updates, you may want to use:
vagrant provision
vagrant provision may be used for two reasons:
A. If for any reason, you had stopped through the process and want to continue where you left off.
B. If you update your ansible recipe, and you want to update your virtual machine.
Terminal Message 3: You may receive this error if your vagrant version is older than version 1.5.4
To check type vagrant -v in your terminal.
To fix it; update your vagrant and run $ vagrant up again.
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:
vm:
* The box 'ubuntu/trusty64' could not be found.
vagrant ssh
Your terminal prompt should change from your normal one.
For example:
(These are not exact, the will vary from computer to computer)
Your terminal prompt before: OSX@jennifer~/myworkfiles $
Your terminal prompt after: vagrant@vagrant-ubuntu-trusty-64:~$
Once you have typed vagrant ssh and your terminal prompt has successfully changed to a new one such as vagrant@vagrant-ubuntu-trusty-64:~$ this means you are now using the terminal of another operating system!
The whole reason you are using Vagrant is to have another operating system (within your computer) to have a completely isolated environment for development.
Type cd /vagrant. This will put you in your virtual machine's Shared Directory.
(See "Understanding Shared Directories" below):
If you want to use your own application (like from Hartl's www.RailsTutorial.org, for example) this is a good place to start.
For example:
(This is only one way to do it. Similar to Hartl's tutorial in Section 1.3).
Once you are in the /vagrant directory, you could:
- Install Rails gem, specifying version
gem install rails -v 4.2.0.beta4 - Create a new directory to hold all of your Rails applications
mkdir workspace - Move into the workspace directory
cd workspace - Create new Rails app, specifying version
rails _4.2.0.beta4_ new example_app
(Hartl Section 1.3, Section 2.1, Section 3.1, etc.) - A new Rails app should have run "bundle install" automatically, but if it did not, run
bundle install - Move into your new application directory
cd example_app - Run the rails server. Running the rails server in Vagrant needs additional parameters (see STEP TEN).
Instructions needed to launch Rails server locally, while in a Vagrant remote OS:
While in the /vagrant shared directory, once new application setup is complete, you may skip to STEP TEN to launch the rails server.
(You can skip to STEP EIGHT if you understand how Vagrant shares directories)
There is now a SHARED DIRECTORY between the two operating systems.
Terminology:
Your normal computer's OS is called: the host OS
The new computer's OS, you created in VirtualBox, is called: the remote OS
First off, let's get our bearings.
vagrant ssh opened a connection between the two computers, and automatically you are now using the terminal of the remote OS.
- After you have done
vagrant ssh - After the terminal prompt change to something like
vagrant@vagrant..:~$ - You are now navigating the terminal of the remote OS.
Now, in the remote OS, try to list all of your files and directories, by typing ls.
You will likely get no results (or only a file or two). You will not see a list of directories.
Though you did not see any directories, you CAN access the shared directory:
Access the shared directory by typing cd /vagrant
- This may feel counter-intuitive. You just tried listing directories by tying
lsand there were no results. - Still, you CAN CHANGE INTO THE SHARED DIRECTORY by typing
cd /vagrant. "vagrant" is the default name given to your shared directory (specified at setup).
You can think of your shared directory as a portal between two operating systems. That means that you can access your files from two locations: (1) in your virtual machines operating system (the remote OS), and (2) from your normal computer(the host OS).
(1) Accessing the file through your remote OS:
(After typing cd /vagrant)
Once again, type ls.
You will see a list of directories populated by the Groundwork project (This does not come standard. The Groundwork repo provided you with extra files and directories. You can navigate these directories as you normal would.)
(2) Access the files through your normal machine:
In a seperate terminal (or however you usually browse through files and directories)...
Go to the directory where you cloned Groundwork (from STEP FOUR)
These are the exact same files accessible from two locations. If you edit them in one place, they are edited in the other.
The Groundwork project has seeded you with these starter directories and files.
You can play with them by typing cd /application/web
(This is the same as STEP EIGHT)
You are now in a rails directory. Go to STEP NINE.
cd /vagrant/application/web
bundle install
rake db:create db:migrate
rails server -b 33.33.33.33
Go to your browser and open http://33.33.33.33:3000