fpiesche commented on PR #19: URL: https://github.com/apache/tika-docker/pull/19#issuecomment-1986672882
Sorry for dropping off the radar - I've had a lot of Life coming at me over the past few months so until fairly recently a lot of my personal github stuff fell by the wayside. It's getting late here but I'll make some time to sort out that regex tomorrow. As for the Docker username/token, adding your personal account/token to the github repo as secrets would indeed be the approach with this workflow. Does the ASF maybe have the ability or a process for setting up org-level accounts for things like accessing project Docker repos for builds (so eg. to have an `apache-tika` account that's controlled by the ASF and just has a Docker Hub access token for external CI processes etc)? I don't have a Docker subscription myself so I honestly have no idea how the Docker Hub CI works or how it would be configured to build on ARM - this workflow wouldn't apply for that process at all :thinking: I had set the GH workflow up on my personal repository as running builds on GitHub's CI and then pushing them to Docker Hub and GHCR from there is how I handle most of my hobby Docker projects, but as those have just me working on them I hadn't run into the token sharing problem... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
