Browse Source

Add Vagrant development environment support

Effy Elden 5 years ago
3 changed files with 119 additions and 0 deletions
  1. +3
  2. +30
  3. +86

+ 3
- 0
.gitignore View File

@ -22,3 +22,6 @@ public/assets
# Ignore Vagrant files

+ 30
- 0 View File

@ -117,6 +117,36 @@ Which will re-create the updated containers, leaving databases and data as is. D
Docker is great for quickly trying out software, but it has its drawbacks too. If you prefer to run Mastodon without using Docker, refer to the [production guide]( for examples, configuration and instructions.
## Development with Vagrant
A quick way to get a development environment up and running is with Vagrant. You will need recent versions of [Vagrant]( and [VirtualBox]( installed.
Install the latest version for your operating systems, and then run:
vagrant plugin install vagrant-hostsupdater
This is optional, but will update your 'hosts' file when you start the virtual machine, allowing you to access the site at (instead of http://localhost:3000).
To create and provision a new virtual machine for Mastodon development:
git clone
cd mastodon
vagrant up
Running `vagrant up` for the first time will run provisioning, which will:
- Download the Ubuntu 14.04 base image, if there isn't already a copy on your machine
- Create a new VirtualBox virtual machine from that image
- Run the provisioning script (located inside the Vagrantfile), which installs the system packages, Ruby gems, and JS modules required for Mastodon
Once this has completed, the virtual machine will start a rails process. You can then access your development site at (or at http://localhost:3000 if you haven't installed vagrants-hostupdater). Any changes you make should be reflected on the server instantly.
When you are finished with your session, run `vagrant halt` to stop the VM. Next time, running `vagrant up` should boot the VM, and skip provsioning.
If you no longer need your environment, or if things have gone terribly wrong, running `vagrant destroy` will delete the virtual machine (after which, running `vagrant up` will create a new one, and run provisioning).
## Contributing
You can open issues for bugs you've found or features you think are missing. You can also submit pull requests to this repository. This section may be updated with more details in the future.

+ 86
- 0
Vagrantfile View File

@ -0,0 +1,86 @@
# -*- mode: ruby -*-
# vi: set ft=ruby :
$script = <<SCRIPT
cd /vagrant # This is where the host folder/repo is mounted
# Add repo for Ruby 2.3 binaries
sudo apt-add-repository ppa:brightbox/ruby-ng
# Add repo for NodeJS
curl -sL | sudo bash -
# Add firewall rule to redirect 80 to 3000 and save
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 3000
echo iptables-persistent iptables-persistent/autosave_v4 boolean true | sudo debconf-set-selections
echo iptables-persistent iptables-persistent/autosave_v6 boolean true | sudo debconf-set-selections
sudo apt-get install iptables-persistent -y
# Add packages to build and run Mastodon
sudo apt-get install \
git-core \
ruby-build \
libpq-dev \
libxml2-dev \
libxslt1-dev \
imagemagick \
nodejs \
ruby2.3 \
ruby2.3-dev \
ruby-switch \
redis-server \
redis-tools \
postgresql \
postgresql-contrib \
# Set Ruby 2.3 as 'ruby'
sudo ruby-switch --set ruby2.3
# Configure database
sudo -u postgres createuser -U postgres vagrant -s
sudo -u postgres createdb -U postgres mastodon_development
# Install gems and node modules
sudo gem install bundler
bundle install
yarn install
# Build Mastodon
bundle exec rails db:setup
bundle exec rails assets:precompile
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| = "ubuntu/trusty64"
config.vm.provider :virtualbox do |vb| = "mastodon"
vb.customize ["modifyvm", :id, "--memory", "1024"]
config.vm.hostname = ""
# This uses the vagrant-hostsupdater plugin, and lets you
# access the development site at
# To install:
# $ vagrant plugin install hostsupdater
if defined?(VagrantPlugins::HostsUpdater) :private_network, ip: ""
config.hostsupdater.remove_on_suspend = false
# Otherwise, you can access the site at http://localhost:3000 :forwarded_port, guest: 80, host: 3000
# Full provisioning script, only runs on first 'vagrant up' or with 'vagrant provision'
config.vm.provision :shell, inline: $script, privileged: false
# Start up script, runs on every 'vagrant up'
config.vm.provision :shell, inline: "cd /vagrant && rails s -d -b", run: 'always', privileged: false