Virtual machine configuration for development environment for bitcoin.
This vagrant configuration can be used to provision a virtual machine locally (using Virtualbox) or remotely on AWS.
What it's doing
Provisioning a bitcoin development environment by grabbing all the dependencies, then building bitcoin from source.
Running the VM
Requirements for both local and remote VMs
- Make sure that vagrant is installed.
- git clone this repository and git clone https://github.com/bitcoin/bitcoin (or a fork) into the same directory. The bitcoin directory will sync into the VM.
Running locally using Virtualbox
- Make sure that Virtualbox is installed.
vagrant upto start the machine.
Running remotely on AWS
- Make sure that the vagrant-aws plugin is installed.
- Super secret AWS config is stored in
Vagrantfile-private-aws. Update that file with your AWS config.
- Use the aws provisioning script to provision the machine:
A note on Vagrant-private-aws
Vagrant-private-aws is checked into the repository. If you change
Vagrant-private-aws and run
git status, it'll show up as modified and unstaged. To suppress that (and stop yourself from accidentally checking in your supersecret AWS config into a public repository), you should run the following command to make git assume that the file is always unmodified:
git update-index --assume-unchanged Vagrantfile-private-aws
What to do next
- log into your VM using
- run bitcoind, run bitcoin tests, etc
- fix bugs, write code, open pull request