Fork: 0
pmarini / nc-env
Download ZIP 2commits
Transfer to URL with SHA
nc-env / templates / template01-nextcloud-standalone /
latest commit f7e1e80e68
@pmarini pmarini authored on 13 Apr 2022
..
artifacts initial commit 3 years ago
Readme.md initial commit 3 years ago
Vagrantfile initial commit 3 years ago
provision.sh initial commit 3 years ago
Readme.md

Stand-alone Nextcloud server

Setup

  • 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
mkcert mkcert command line utility to be downloaded here. Pick the latest binary for amd64 and rename it to mkcert
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