2016-01-04 16:33:20 +01:00
|
|
|
#!/usr/bin/env python3
|
2014-01-09 16:02:09 +01:00
|
|
|
#
|
|
|
|
# You may want to alter these before running ./makebuildserver
|
2013-12-30 17:11:52 +01:00
|
|
|
|
2016-01-21 14:09:12 +01:00
|
|
|
# In the process of setting up the build server, many gigs of files
|
|
|
|
# are downloaded (Android SDK components, gradle, etc). These are
|
|
|
|
# cached so that they are not redownloaded each time. By default,
|
|
|
|
# these are stored in ~/.cache/fdroidserver
|
|
|
|
#
|
|
|
|
# cachedir = 'buildserver/cache'
|
|
|
|
|
2016-01-20 20:40:25 +01:00
|
|
|
# To specify which Debian mirror the build server VM should use, by
|
|
|
|
# default it uses http.debian.net, which auto-detects which is the
|
|
|
|
# best mirror to use.
|
|
|
|
#
|
|
|
|
# debian_mirror = 'http://ftp.uk.debian.org/debian/'
|
|
|
|
|
2017-10-20 15:20:51 +02:00
|
|
|
# The amount of RAM the build server will have (default: 2048)
|
2016-01-20 21:00:16 +01:00
|
|
|
# memory = 3584
|
2013-06-06 11:33:44 +02:00
|
|
|
|
2015-02-01 10:00:04 +01:00
|
|
|
# The number of CPUs the build server will have
|
2016-01-20 21:00:16 +01:00
|
|
|
# cpus = 1
|
2015-02-01 10:00:04 +01:00
|
|
|
|
2016-01-20 21:00:16 +01:00
|
|
|
# Debian package proxy server - if you have one
|
|
|
|
# aptproxy = "http://192.168.0.19:8000"
|
2013-06-06 11:33:44 +02:00
|
|
|
|
2016-01-26 17:35:25 +01:00
|
|
|
# If this is running on an older machine or on a virtualized system,
|
|
|
|
# it can run a lot slower. If the provisioning fails with a warning
|
|
|
|
# about the timeout, extend the timeout here. (default: 600 seconds)
|
|
|
|
#
|
|
|
|
# boot_timeout = 1200
|
2016-09-15 11:12:18 +02:00
|
|
|
|
|
|
|
# By default, this whole process uses VirtualBox as the provider, but
|
|
|
|
# QEMU+KVM is also supported via the libvirt plugin to vagrant. If
|
|
|
|
# this is run within a KVM guest, then libvirt's QEMU+KVM will be used
|
|
|
|
# automatically. It can also be manually enabled by uncommenting
|
|
|
|
# below:
|
|
|
|
#
|
|
|
|
# vm_provider = 'libvirt'
|
2018-10-11 11:30:46 +02:00
|
|
|
|
|
|
|
# By default libvirt uses 'virtio' for both network and disk drivers.
|
|
|
|
# Some systems (eg. nesting VMware ESXi) do not support virtio. As a
|
|
|
|
# workaround for such rare cases, this setting allows to configure
|
|
|
|
# KVM/libvirt to emulate hardware rather than using virtio.
|
|
|
|
#
|
|
|
|
# libvirt_disk_bus = 'sata'
|
|
|
|
# libvirt_nic_model_type = 'rtl8139'
|
2019-01-10 14:48:29 +01:00
|
|
|
|
|
|
|
# Sometimes, it is not possible to use the 9p synced folder type with
|
|
|
|
# libvirt, like if running a KVM buildserver instance inside of a
|
|
|
|
# VMware ESXi guest. In that case, using NFS or another method is
|
|
|
|
# required.
|
|
|
|
#
|
|
|
|
# synced_folder_type = 'nfs'
|