You may want to write a simple bash script that dot sources the .env file followed by the command.
Something like:
. .env
Have the service call this script instead of your command.
You may want to write a simple bash script that dot sources the .env file followed by the command.
Something like:
. .env
Have the service call this script instead of your command.
Otherwise you have two options. Add an [Environment] section to your service.
Or add a .conf file containing the [Environment] section. Somewhere like this:
/etc/systemd/system/
But if your goal is to use a single .env for configuring the service then you may want to go with dot sourcing the .env file.