How to set environment variables in the deployed Runpod based on .env file?

[AWolf81]

Is it possible to set the env. variables during flash deploy?

Something like flash deploy --env production --env-file .env or similar? Is it a planned feature?

I've seen that the .env file is excluded from the artifacts by default PR #280, that's good and I understand it. It's that the .env file is not readable in the Runpod artifacts.

But what is the right way to use env. variable in the deployed Runpod? Do I have to add my env. variables manually in the Runpod UI or with a shell script?

I think I'll do it with a shell script for now.
That's better than doing it manually but it might be a feature worth to add to flash directly.

Thanks for creating the flash tool. I really like it.

[deanq]

Right. We should make this clear in our docs and examples. Meanwhile, here's one example that establishes the pattern: 05_data_workflows/01_network_volumes/gpu_worker.py

@Endpoint(
    name="05_01_gpu_worker",
    env={"HF_HUB_CACHE": MODEL_PATH, "MODEL_PATH": MODEL_PATH},
)

Perhaps a practical pattern would be to have a shared env dictionary if you're expecting uniformed env vars across your endpoints. Then you can just reference them like @Endpoint(name="foobar", env=global_env)