external
/
mailinabox
mirror of https://github.com/mail-in-a-box/mailinabox.git
1
0
Fork 0
Code Issues Releases Wiki Activity
mailinabox/Vagrantfile

29 lines
913 B
Ruby
Raw Normal View History

Vagrantize * adding a Vagrantfile * in a non-interactive setup like this, create the user's first email account for them * let the machine auto-detect its IP address using http://icanhazip.com/ * use our own justtesting.email domain to provision a subdomain for users so they can quickly get started
2014-06-04 23:39:58 +00:00
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
minimal changeset to get things working on 18.04 @joshdata squashed pull request #1398, removed some comments, and added these notes: * The old init.d script for the management daemon is replaced with a systemd service. * A systemd service configuration is added to configure permissions for munin on startup. * nginx SSL settings are updated because nginx's options and defaults have changed, and we now enable http2. * Automatic SSHFP record generation is updated to know that 22 is the default SSH daemon port, since it is no longer explicit in sshd_config. * The dovecot-lucene package is dropped because the Mail-in-a-Box PPA where we built the package has not been updated for Ubuntu 18.04. * The stock postgrey package is installed instead of the one from our PPA (which we no longer support), which loses the automatic whitelisting of DNSWL.org-whitelisted senders. * Drop memcached and the status check for memcached, which we used to use with ownCloud long ago but are no longer installing. * Other minor changes.
2018-07-07 18:41:41 +00:00
config.vm.box = "ubuntu/bionic64"
adds optional vagrant-cachier if you have the plugin installed (#1028)
2017-01-15 15:47:36 +00:00
Vagrant updates * use a public box (the official Ubuntu 14.04 box which contra the description does have VBox Guest Additions installed) * now that we allow SSH password logins, since Vagrant requires it, dont muck with sshd_config here * don't put the machine on the public network because that will allow anyone to log into it with Vagrant's default username/password, duh
2014-06-06 12:20:26 +00:00
# Network config: Since it's a mail server, the machine must be connected
# to the public web. However, we currently don't want to expose SSH since
# the machine's box will let anyone log into it. So instead we'll put the
# machine on a private network.
adding a fully qualified domain name for the hostname and ignoring the .vagrant dir (#1027)
2016-12-20 21:32:06 +00:00
config.vm.hostname = "mailinabox.lan"
Vagrant updates * use a public box (the official Ubuntu 14.04 box which contra the description does have VBox Guest Additions installed) * now that we allow SSH password logins, since Vagrant requires it, dont muck with sshd_config here * don't put the machine on the public network because that will allow anyone to log into it with Vagrant's default username/password, duh
2014-06-06 12:20:26 +00:00
config.vm.network "private_network", ip: "192.168.50.4"
Vagrantize * adding a Vagrantfile * in a non-interactive setup like this, create the user's first email account for them * let the machine auto-detect its IP address using http://icanhazip.com/ * use our own justtesting.email domain to provision a subdomain for users so they can quickly get started
2014-06-04 23:39:58 +00:00
config.vm.provision :shell, :inline => <<-SH
auto-agree to Let's Encrypt's terms of service during setup fixes #1409 This reverts commit 82844ca651fa31755878490eabca0d80e83f8bda ("make certbot auto-agree to TOS if NONINTERACTIVE=1 env var is set (#1399)") and instead *always* auto-agree. If we don't auto-agree, certbot asks the user interactively, but our "curl | bash" setup line does not permit interactive prompts, so certbot failed to register and all certificate things were broken until the command was re-run interactively.
2018-09-03 16:52:03 +00:00
# Set environment variables so that the setup script does
# not ask any questions during provisioning. We'll let the
# machine figure out its own public IP.
replace '-t 0' test with an environment variable since '-t 0' is false when standard input has been redirected and doesn't tell us whether or not we can use dialog for input, but Vagrant must be non-interactive
2014-08-25 11:54:11 +00:00
export NONINTERACTIVE=1
add comments to the new get_default_hostname etc. functions, and simplify the logic in the Vagrantfile and start.sh so that we always call into the same two functions
2014-06-07 18:55:57 +00:00
export PUBLIC_IP=auto
Support dual-stack IPv4/IPv6 mail servers Addresses #3 Added support by adding parallel code wherever `$PUBLIC_IP` was used. Providing an IPv6 address is completely optional. Playing around on my IPv6-enabled mail server revealed that — before this change — mailinabox might try to use an IPv6 address as the value for `$PUBLIC_IP`, which wouldn't work out well.
2014-06-08 22:32:52 +00:00
export PUBLIC_IPV6=auto
remove all references to justtesting.email (#1003) (#1005)
2016-11-30 17:55:18 +00:00
export PRIMARY_HOSTNAME=auto
local changes reverted
2020-11-05 19:05:05 +00:00
#export SKIP_NETWORK_CHECKS=1
Vagrantize * adding a Vagrantfile * in a non-interactive setup like this, create the user's first email account for them * let the machine auto-detect its IP address using http://icanhazip.com/ * use our own justtesting.email domain to provision a subdomain for users so they can quickly get started
2014-06-04 23:39:58 +00:00
# Start the setup script.
cd /vagrant
setup/start.sh
SH
end