The reason that phoenix takes precedence in our launcher is because we check that the app has releases setup and create these files as needed. In the order of the framework scanners Phoenix comes before the Dockerfile one. This is something I’m particularly interested in revisiting at some point to be honest!
As for your secrets in Dockerfile. Fly.io secrets are runtime only and Dockerfile envs are compile time. To add secret things there you should use build arguments. Here’s some tips from previous conversations in our community forum:
- Secret docker build arguments
- What is the correct workflow for utilising secrets during deployment? - #8 by jsierles
Thanks for the feedback, we will add that to our backlog.