Secure Matomo Provision
With support for local provisioning via Vagrant (useful to quickly testing changes).
Both local and non-local provisions were tested on a Ubuntu 18.04 instance.
- Requires Vagrant to be installed.
Then navigate to https://localhost:8443/. Note: because it is using a self-signed certificate, you will receive a warning when opening the page within a browser.
Provisioning a Production, i.e. Remote, Site
- Requires Ansible to be installed.
First make sure there is a remote Ubuntu 18.04 instance that you want to install Matomoo on. Also, make sure you can ssh in, i.e. running the command
ssh firstname.lastname@example.org should be successful.
Then make sure to update the inventory's
[prod] my-matomo-instace.com ansible_user=root
Running the playbook to provision the instance
certificate_domain to be set. These can be passed as extra vars when invoking the playbook:
ansible-playbook -i inventory site.yml -e "email@example.com" -e "certificate_domain=my-matomo-instace.com"
Default Database Credentials
db_username: matomo db_password: 'Jana705&loge'
These can be overridden by passing in extra vars like in the above command.
Other Configuration Notes
Make sure to off the Archive reports when viewed from the browser settings option. The provision creates a cron job to automatically archive reports.