source envvars before service run

[jack1902]

to:
cc: @subspacecommunity/subspace-maintainers
related to:
resolves: #90 #97

Background

Bug reports were raised and this is how i can fix it. There MIGHT be a better solution than this in terms of using KEY=VALUE as part of the below. But i personally feely like this approach is better as ALL environment variables are only relevant to subspace

subspace/bin/my_init

Line 30 in 15ff6db

exec env - PATH=$PATH runsvdir -P /etc/service &

Changes

• source the /etc/envvars file before calling subspace

Testing

• Ran locally by adding env > /data/wireguard/environment to entrypoint.sh line 179 and observed the expected envvars as passed in from docker-compose

[elliotwestlake]

🆗