Hopefully this is the right place for this.
Summary
I would like to install Mattermost in my Apache vhost directory instead of /opt so that each domain can have it's own forums in a virtual hosting environment.
Steps to reproduce
I have followed the Debian Jessie install instructions with Postgres, my vhosts are managed by the latest version of virtualmin (5.04). I am also running Mattermost 3.2.0. Debian and all packages are fully upgraded and running the latest versions. I am only running packages from the official debian repositories.
To reproduce my setup, install the latest debian, selecting only ssh server - no other services or desktops. Download and install the free 10 doamin version of Virtualmin which will install and configure apache, email, etc. Install PostgreSQL from inside Virtualmin. Virtual hosting will also be setup. Create a domain and enable PostgreSQL as the database for that domain, then create a subdomain. Install Mattermost into the subdomain (or parent domain if you prefer) following the Mattermost installation guide for Debian Jessie but not installing Postgres as it is already installed. Integrate the vhost info into the domain.conf or sub.domain.conf depending on where you want to access Mattermost. After following the instructions including tests, you should have a functioning install.
Now try having Mattermost run from /home/domain/mattermost or /home/domain/domains/sub-domain/mattermost or even just put the data directory in those locations with permissions for the mattermost directory structure owned by mattermost:mattermost.
Alternatively, leaving mattermost fully installed and running from /opt/mattermost, create domain2 and then set it up so that it also accesses the same server - without exposing the first domains teams.
Expected behavior
I would like to be able to have mattermost run completely from inside a vhost so that I can cleanly migrate or backup all domain assets as the occasion arises.
Observed behavior
Everything is working from /opt/mattermost, but if I move it to /home/domain/mattermost then it does not run, or try to put the data directory in /home/domain/mattermost/data then none of that profile images work, etc.
Alternatively, I want to be able to run mattermost from domain, domain1, etc. I haven't tried this config yet and it might actually work. I will hopefully be testing the second option in the next couple of days, but it would still be nice to have the data stored in the domain for migration purposes as well as backup and restore.