emonSD issues created using new scripts + emonhub environment file

I think Im edging towards the Environment file solution for setting the service paths and using /opt/emon/emonhub directly.

We discussed the use of /opt over /usr here:
https://community.openenergymonitor.org/t/emonsd-next-steps/10426/106 @djh said:

Given that in this case the distro is not packaging the ‘product’ is it not therefore correct to use /opt directly?

The precise location aside, one of the goals of this installation script is to provide flexible installation paths rather than nailing everything down. I know we are still a number of steps away from that (e.g /var/www discussion), but perhaps using the environment file to allow emonhub to either be installed by our installer or perhaps if someone wants to do so be packaged independently and installed by the distro into /usr/local or other relevant location?

I haven’t tried using an environment file with systemd yet so I’m assuming this is possible and not bad practice