.vagrantuser.example
author Connor Sheehan <sheehan@mozilla.com>
Wed, 03 Jul 2019 11:28:49 -0400
changeset 7093 1e55b3601d0a82bb1003aa495b3b296407640b14
parent 4762 aa4898f3eea22d02629e888071f285d420d68f2b
permissions -rw-r--r--
readonly: print `hg serve` error log at end of test When something fails inside the `hg serve` process, this will cause it to be printed out in the test.

# vim:ft=yaml:
# Example .vagrantuser file for customizing the version-control-tools VM.
# See the top of the project Vagrantfile for how to use this file.

# The private IP the vagrant VM should use on startup.
#private_ip: "192.168.33.33"

# The number of CPUs to assign to the vagrant VM.
#cpus: "2"

# The amount of memory to assign to the vagrant VM.
#memory: "2048"

# Display the virtual machine management GUI on VM startup.
#show_gui: false

# The folder that should be synced into the vagrant VM at /home/vagrant/vct.
# Defaults to the project root folder, '.'.
#synced_folder: "."

# The ansible playbook vagrant should run when configuring the development
# machine.  You can override or augment the default vagrant guest configuration
# by setting this to your custom playbook and using "- include:" to pull in the
# default playbook.
#
# Note that this path is relative to the /vagrant synced directory on the
# guest.  You will need to place your custom playbook under the project root
# for it to get synced into the guest and called.
#playbook: "testing/vagrant/configure.yml"

# How verbose ansible should be while configuring the vagrant box.  Helpful for
# debugging.
#ansible_verbose: "vvv"

# Extra ansible command-line args that override everything else.
# See https://www.vagrantup.com/docs/provisioning/ansible_common.html#raw_arguments
#ansible_args: ['--check']