Is it possible to put the env.yaml file anywhere and not just in $HOME/.sling

[ShahBinoy]

This is to allow just the definition to be placed along the code base, use relative paths or produce in different location in Docker.
Forcing the file to be in $HOME/.sling is a bit too restrictive.

Or is it allowed/possible to pass in the env.yaml file as a CLI argument.

[flarco]

Yes, just provide env var SLING_HOME_DIR

[ShahBinoy]

Thank You.