You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if sharing publicly available docker image wouldn't be an enabler for this project. Surely each user could build and push their images to their private repos, but that's extra work repeated possibly numerous times. I'd expect that having maintainer-approved ready-to-use images would decrease the learning curve and foster adoption.
When it comes to implementation, I'd expect that it should be quite straightforward to push to an additional repository - private GCP repo support is already there (it possibly could be reused/extended).
WDYT?
The text was updated successfully, but these errors were encountered:
building docker image from git tag docker build https://github.com/allegro/turnilo.git#1.39.0 -t turnilo:1.39.0
question - after I have the built docker image , do I have any option to set env variable to inject / set path to my config.yaml file ?
suggest to have set of docker enviriment params
can look on this as example (outdated) - https://hub.docker.com/r/uchhatre/turnilo
need easy way to inject to turnilo the config.yaml file , and druiid cluster url
I wonder if sharing publicly available docker image wouldn't be an enabler for this project. Surely each user could build and push their images to their private repos, but that's extra work repeated possibly numerous times. I'd expect that having maintainer-approved ready-to-use images would decrease the learning curve and foster adoption.
When it comes to implementation, I'd expect that it should be quite straightforward to push to an additional repository - private GCP repo support is already there (it possibly could be reused/extended).
WDYT?
The text was updated successfully, but these errors were encountered: