nc-env/templates/template01-nextcloud-standalone at 6ad42a6221bbee9a77c56b0a4d0f16afde3c3792


..
artifacts	- template01, provision.sh: add crontab and set it as the background jobs execution agent	2 years ago
Readme.md	adapt the template files to the new OS image, based on Ubuntu Server 22.04 LTS	3 years ago
Vagrantfile	adapt the template files to the new OS image, based on Ubuntu Server 22.04 LTS	3 years ago
provision.sh	- template01, provision.sh: add crontab and set it as the background jobs execution agent	2 years ago

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

File name	Description
`nc-fulltext-live-indexer.service`	OPTIONAL - systemd unit file for the Fulltext live indexer
`nc-redirect.conf`	Apache Web Server http-to-https redirect configuration file
`nextcloud.conf`	Apache Web Server main configuration file
`nextcloud-X.Y.Z.tar.bz2`	The installer archive to be downloaded from here
`nextcloud-X.Y.Z.tar.bz2.md5`	md5 signature of the installer archive to be downloaded from here
`occ`	Alias for the occ command
`redis.conf`	Redis server configuration file
`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 change the value of variable lxd.name. It makes sense to give the same name as the folder, in this example nc-instance.
Open provision.sh
- change the value of variable MACHINE_HOSTNAME. It makes sense to give the same name as the folder, plus the domain, in this example nc-instance.localenv.com.
- change the value of variable NEXTCLOUD_INSTALLER_ARCHIVE to match the name of the installer archive you are using.
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
Start using your environment