Web hosting

All members have access to web hosting with no limit on the number of domains/sites. There is a unenforced limit of 300Mb per site. Web hosting is done on osprey only at this time. Access to CDN storage and serve via BunnyWay d.o.o. is planned.

Currently, webroots can only be stored on osprey. This makes things relatively simple — you can either :

1. Set a CNAME record for either :
   • osprey.birb.fr. to point directly to osprey
   • eur.doamatto.xyz. to point to osprey and any future shared webroots based in Europe
2. Set an A and AAAA record for 167.235.131.220 and 2a01:4f8:1c1b:9f00::1, respectively.

CAA records and switching certificate authorities

Some people may utilise CAA records to ensure only trusted certificate authorities can issue TLS certificates. By default, all webroots use Buypass AS for TLS certificates. You can add the following records to trust certificates issued by Buypass AS :

caa-example.birb.fr. CAA 0 issue "buypass.no"
caa-example.birb.fr. CAA 0 issuewild "buypass.no"

Some individuals may prefer using alternative free ACME providers — such as Let's Encrypt or ZeroSSL — or a paid provider such as DigiCert or SwissSign. To switch, set the value of tls.acme to set your ACME URL.

• DigiCert ACME URL — https://one.digicert.com/mpki/api/v1/acme/v2/directory
• Let's Encrypt ACME URL — https://acme-v02.api.letsencrypt.org/directory
• SwissSign ACME URL — https://acme.swisssign.ch/v1/ACME-URL/directory
• ZeroSSL ACME URL — https://acme.zerossl.com/v2/DV90

acme-example.birb.fr {
	tls {
		acme {url}
	}
}

If you switch certificate authorities, you can find the necessary records to trust via the SSLMate/caa_helper project. There is no planned support for manual certificate uploads or private ACME providers at this time.

Subpages

• Caddy snippets
• Updating your webroot