On Wed, Jul 01, 2020 at 06:25:47PM +0200, Adrian Reber wrote: > > No, this part only needs to talk read-only to the database. This is not > touching anything on the disk besides writing the output. I guess you > were thinking about the umdl (update-master-directory-listing) part. > That would need ro access to the file-system. Right. I was actually thinking of both. ie, at some point down the road it might be a nice thing to get all of mirrormanager in openshift. Each part could be a seperate project or under one or all as various toddlers, but I think in the end it would make it more maintainable and also open up some improvements on workflow... not to say we couldn't also do this without moving everything to openshift, but I openshift has some nice advantages from the operations side anyhow. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
