Manual Configuration

Manual Configuration

If you customize your installer script or if you install Site Wrangler by hand, you may need to configure Site Wrangler to work with your custom setup.

To change settings, you can use a command similar to this one:

sw setting set nameserver_one ns1.example.com

Alternatively, You can change settings in the file “/opt/sitewrangler/etc/config”. Each setting must follow this format within that file:

nameserver_one: ns1.example.com

It is important to note that updating setting values does not update configuration files that used the setting when the file was generated. For example, updating the nameservers does not update your DNS zone files to use the new nameservers.

local_ip

default:

The local IP address

public_ip

default:

The public IP address

install_path

default: /opt/sitewrangler/

If Site Wrangler is not installed in it’s usual place, you must specify the file path to where Site Wrangler is installed.

nameserver_one

default: ns1.example.com

Whenever new DNS zones are created, they are created with NS records. This setting is used as the first domain included in those records. This value should point to this server.

nameserver_two

default: ns2.example.com

Whenever new DNS zones are created, they are created with NS records. This setting is used as the second domain included in those records. This value should point to this server.

dns_authority

default: dns-admin.example.com

All DNS zones must include an SOA with an authority value. This setting is used as the domain in this record. This value should point to this server.

email_admin_on_build_success

default: True

Whenever the system fails to build software, the system administrator will be email. You can also optionally be notified of successful builds as well.

mail_shadow_file

default: /etc/dovecot/shadow

If you do not use the the default path for your email shadow file, you can set it via this value.

mail_domain_file

default: /etc/maildomains

Site Wrangler uses a domain dictionary for associating mail domains with system users. If you use a different path for this file

dkim_folder

default: /etc/exim4/dkim/

This folder is used to store a copy of both the public and private DKIM keys.

exim_folder

default: /etc/exim4/

The path to exim’s configuration folder. This is used to store a copy of the certificates for each domain and it’s subdomains. Within this folder, the certificates and keys will be stored in ‘ssl/certs’ and ‘ssl/private’.

system_admin_email

default: root@localhost

Whenever the system administrator needs to be notified, such as when a build fails, this email address will be used.

exim_user

default: Mail

The system user that Exim runs under. This value is used to ensure file permissions are correct.

exim_group

default: Mail

The system group that Exim runs under. This value is used to ensure file permissions are correct.

imap-distro

default: unset

This value is the operating system code used when building uw-imap. Upon first build, you will be prompted to select this value if it cannot be auto-detected.

owasp-modsec-branch

default: v3.0/master

When fetching the OWASP rule set for ModSecurity, use this git branch.

enable_php_legacy_versions

default: False

Setting this to true will allow you to install PHP versions 7.0 and 5.6.

enable_php_super_legacy_versions

default: False

Setting this to true will allow you to install PHP versions prior to 7.0 and 5.6. This is untested. You will need to make your own build configuration for these PHP versions.

Leave a Reply

Your email address will not be published. Required fields are marked *