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
Thank you for updating the project. I generally use the docker image. I realized using ghcr might be a nice opportunity to maintain an up to date image. I experimented a bit and developed some github actions that auto publish docker containers if a release is made. See: https://github.com/bart1/brother_ql_web/pkgs/container/brother_ql_web . Would you appreciate a pull request?
The text was updated successfully, but these errors were encountered:
Thanks for the request and sorry for the delay - I missed watching my own fork for changes. I am (mostly) not using Docker myself (only if I need to build manylinux wheels), thus I did not yet bother about this and I am not really sure what the correct approach is here.
How much maintenance work can be expected for the Docker images, even if automated? How can we ensure appropriate handling of Docker-specific issues? Additionally, which credentials are required here and to which extent would this lead to any costs on my side?
Thank you for updating the project. I generally use the docker image. I realized using ghcr might be a nice opportunity to maintain an up to date image. I experimented a bit and developed some github actions that auto publish docker containers if a release is made. See: https://github.com/bart1/brother_ql_web/pkgs/container/brother_ql_web . Would you appreciate a pull request?
The text was updated successfully, but these errors were encountered: