-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: pictrs-safety #175
feat: pictrs-safety #175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give it a more in-depth look later :).
Thanks for the PR!
From a code standpoint it looks fine now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@codyro once it looks good to you, feel free to merge.
Everything looks good/tested on the normal targets. At some point, we should consider showing an example of using SSL/TLS so the pictrs-safety<->worker data can be encrypted (image body is sent). |
Adds inventory variable to enable picts-safety
pictrs gets an extra conditional for a new variable
PICTRS__MEDIA__EXTERNAL_VALIDATION
to connect the validation to pictrs-safety.I used `{{ domain }} for it, as I don't know how otherwise to tell pictrs which IP to connect. Feel free to adjust to use some internal IP. My docker knowledge is very superficial.
Likewise, the pictrs-safety port is supposed to be exposed to the internet to allow workers to connect to it.
Currently I'm using the
:main
version as I'm having trouble pushing versioned docker images to ghcr.io. I'm trying to figure that out.