I’m wondering how y’all are adding fly-log-shipper to your applications?
I’ve added the repo as a git submodule so I can keep my local copy up to date with any new PRs from the maintainers. The problem is I need to supply [env] values in the fly.toml file. This obviously causes a change that git picks up on. I don’t want to create a branch and push these changes to the origin.
I’m wondering if y’all are copy and pasting this repo into your project and tracking is as a part of your project. Or are you forking this project and creating your own version?
Usually ran as a separate Fly app (a shared-1x cpu with 256mb mem should be enough is my guess) on a forked repo. Typically, you’d keep main unchanged and in-sync with upstream, and merge that main into your own branch with changes specific to your app carried forward, forever.
Or, you can instructfly deploy to ignore values in fly.toml by supplying either a different my.fly.toml with the --config switch, or by supplying args against --env, --app etc to fly deploy itself.
Thanks for the information.
For the main time am setting the Env as this flyctl deploy --build-secret FUSION_AUTH_URL=$FUSION_AUTH_URL --remote-only
This was able to set the environment variable but this issue is that when i tried to set multiple key it does not run at all flyctl deploy --build-secret FUSION_AUTH_URL=$FUSION_AUTH_URL --build-secret FUSION_AUTH_PUBLIC_KEY=$FUSION_AUTH_PUBLIC_KEY
I haven’t needed this, so I can’t tell if it stopped working now or whether it was never supposed to work this way (cc: @fideloper-fly), but I want to point out that you can always pass multiple --build-args to fly deploy (ref) and set them as ENVs in dockerfile which are then available as env vars to your app instance running on Fly. nb, it is not recommended to use --build-arg for sensitive data.