nc-env/templates/template05-elasticsearch at v20230420


..
artifacts	initial commit	3 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	use env in Vagrantfile to provide environment variables; do not create additional system user; update base image from Vagrant cloud	2 years ago
provision.sh	use env in Vagrantfile to provide environment variables; do not create additional system user; update base image from Vagrant cloud	2 years ago

As of March 2023, Nextcloud Full Text Search requires ElasticSearch 7, it's not compatible with ElasticSearch 8

Elastic Search is quite resource-intensive so that you may want to create a dedicated LXD profile and assign the container to that profile (property `lxd.profiles`)

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

File name	Description
`elasticsearch-${ELASTICSEARCH_VERSION}-amd64.deb`	Debian archive for version 7.17.X to be downloaded from here
`memory.options`	Limit the total memory assigned to the JVM
`elasticsearch.yml`	ElasticSearch core configuration file

Open Vagrantfile and assign a value to the following variables and parameters:
- lxd.name (it is recommended to give the same name as the folder, in this example elasticsearch-instance)
- MACHINE_HOSTNAME
- ELASTICSEARCH_VERSION
Create folder log
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 by setting up the LXD nameserver
Start using your environment