What about:

    source <(cat .env | xargs)

or:

    export $(cat .env | xargs)

And then:

    unset $(cat .env | cut -d= -f1)

?

The last one unsets the environment variables that were set by the first command, ensuring they are not persisted beyond the current shell session.

If you are worried about forgetting to execute it, there are a couple of ways to work around it, depending on your case.

Yes, you can build fully server rendered web apps with Phoenix. You'd need HTML templates for that though, so you shouldn't use the --no-html option.

--no-webpack is deprecated as Phoenix uses esbuild now but see the docs: "--no-esbuild - do not include esbuild dependencies and assets. We do not recommend setting this option, unless for API only applications, as doing so requires you to manually add and track JavaScript dependencies"

There is a vast gap between walled garden cloud service rent seeking and giving away software as open source. In the olden days you could buy software licenses to run it wherever you wanted.