nc-env/templates/template02-collabora-online at 203ca80c2caabb321583cdadb4f40a5eb5e0c90f


..
artifacts	use env in Vagrantfile to provide environment variables; do not create additional system user; update base image from Vagrant cloud	2 years ago
Readme.md	use env in Vagrantfile to provide environment variables; do not create additional system user; update base image from Vagrant cloud	2 years ago
Vagrantfile	update Readme and adapt template to new Vagrant box, based on Ubuntu 24.04	9 months ago
provision.sh	update Readme and adapt template to new Vagrant box, based on Ubuntu 24.04	9 months ago

Assuming that the copy of the template is called collabora-instance, move to folder collabora-instance.
Check the content of folder artifacts

File name	Description
`collaboraonline.sources`	Apt sources file for Collabora packages
`coolwsd.xml`	Configuration file for the Collabora server
`coolwsd.service`	Systemd service file for Collabora server
`rootCA.pem`	The rootCA previously created in your host machine
`rootCA-key.pem`	The rootCA key previously created in your host machine

Create folder log
Open Vagrantfile and assign values to the following parameters or variables:
- lxd.name (it is recommended to give the same name as the folder, in this example collabora-instance)
- MACHINE_HOSTNAME
- CO_VERSION
- CUSTOMER_HASH (only for Enterprise Edition)
Run vagrant up > log/provisioning.log
Make sure your system is able to resolve the domain name that you specified in variable MACHINE_HOSTNAME, for example by adding an entry in /etc/hosts or configure a nameserver in LXD
Start using your environment