Vagrant installer for cloudfoundry ng
Ruby Shell
Pull request Compare This branch is 301 commits ahead, 1 commit behind gramos:master.
Latest commit 5f6d24f Aug 4, 2014 @mgarciap mgarciap Merge pull request #111 from hingstarne/master
Fixed metadata for Ridley. Thanks @hingstarne
Failed to load latest commit information.
bin Replacement of for Sep 20, 2013
chef Fixed metadata for Ridley Aug 4, 2014
cloud_controller_ng @ 518def6 bump cc version Jun 20, 2013
custom-buildpacks Update Sep 20, 2013
custom_config_files Replacement of for Sep 20, 2013
db store cf components dbs. CC so far May 18, 2013
dea_ng @ 36472df bump version to cf-release release-candidate versions Jun 20, 2013
gorouter @ e24516c reverting to e24516c Jun 21, 2013
health_manager @ 93f0e11 bump version to cf-release release-candidate versions Jun 20, 2013
init There is no need for /vagrant/log Sep 16, 2013
logs .gitkeep makes more sense May 17, 2013
test lets add more CF environment variables Sep 20, 2013
uaa @ 020f00b Replaced travisci base box with precise64 box to enable non-Virtualbo… May 14, 2013
vmware Attempt to automate vmware setup Jul 2, 2013
warden @ 2fd4fcd bump version to cf-release release-candidate versions Jun 20, 2013
.gitattributes Add documentation, changes and scripts for VMware Workstation 9 support. May 22, 2013
.gitignore Attempt to automate vmware setup Jul 2, 2013
.gitmodules Change Warden repo url from ssh to https. No more github account depp… Oct 18, 2013
Berksfile Fixing to a specific version of the apt cookbook, version 1.10.0 - as… Jun 11, 2013 forgot it was a markdown Jun 28, 2013 Run Local URL changed Mar 7, 2014
Rakefile Bundle install failures during bootstrap should be obvious Nov 27, 2013
Vagrantfile Merge pull request #103 from mdlavin/fix-issue-98 Dec 13, 2013 Rapidly start, stop and check the status of CF Sep 20, 2013 Rapidly start, stop and check the status of CF Sep 20, 2013 Rapidly start, stop and check the status of CF Sep 20, 2013


This project is no longer actively maintained. There are other updated alternatives to install CF. Chech out:


This project provides a mechanism to automate several tasks to be able to set up a Vagrant VM with the following V2 (NG) Cloud Foundry components:

  • Cloud Controller
  • NATS
  • DEA
  • Gorouter
  • UAA
  • Warden
  • Health Manager


  • Vagrant

    • Download it from (version 1.2 or higher)
    • Install required plugins: vagrant plugin install vagrant-berkshelf vagrant plugin install vagrant-omnibus
  • Ruby 1.9.3

  • (Optional) The VMware Fusion or VMware Workstation provider. If you do not have these installed, you can use the default VirtualBox provider (

    • Fusion: vagrant plugin install vagrant-vmware-fusion vagrant plugin license vagrant-vmware-fusion license.lic

    • Workstation: vagrant plugin install vagrant-vmware-workstation vagrant plugin license vagrant-vmware-workstation license.lic


Clone the repo

git clone
cd cf-vagrant-installer

want to try a particular version?

git checkout tags/v1.0.0

Initialize submodules

rake host:bootstrap

Provision The VM

Using VirtualBox

Initialize the Vagrant VM using the default VirtualBox provider.

vagrant up

Using VMware Fusion / Workstation

Alternatively, you can use a different Vagrant provider such as the VMware Fusion or VMware Workstation provider. See the Vagrant documentation for information on installing and using providers.

Stop!! If you are going to use the VMware provider, you must follow the instructions here first, or the next steps will result in an environment that will not work.

Fusion: vagrant up --provider=vmware_fusion
Workstation: vagrant up --provider=vmware_workstation

Running Cloud Foundry

Cloud Foundry will be bootstrapped the first time the Vagrant provisioner runs (it may take several minutes). After the bootstrap is complete, an upstart configuration will be generated to automatically start Cloud Foundry at boot.

The following commands may be helpful if you wish to manually start and stop Cloud Foundry.

# shell into the VM if you are not already there
vagrant ssh
cd /vagrant

# List the status of each CF component

# Start Cloud Foundry

# Also, to stop:

Test Your New Cloud Foundry (v2) Instance

Make sure your CF is up and running

  • Set up your PaaS account
# from the directory where you cloned the repo
rake cf:init_cf_cli
  • Push a very simple sinatra application
cd test/fixtures/apps/sinatra
cf push

Expected output:

Using manifest file manifest.yml

Creating hello... OK

Binding to hello... OK
Uploading hello... OK
Preparing to start hello... OK
Checking status of app 'hello'...
  0 of 1 instances running (1 starting)
  1 of 1 instances running (1 running) # This may vary

Open a browser and check if the app has been deployed:

Sinatra Test app for CF Vagrant Installer

Hello from!
..... Some environment info .....

Use "cf apps" command to list the apps you pushed:

cf apps
Getting applications in myspace... OK

name    status    usage      url
hello   running   1 x 256M

There is also a node.js sample app in test/fixtures/apps

Custom buildpacks power

Now you can test any buildpacks (3rd party, or your own) with cf-vagrant-installer

  • How does it help?
  • What are the use cases?
  • What are they?
  • Step by step example
  • Continue reading

Cloud Foundry documentation


You are welcome to contribute via pull request.