Last modified: 2013-08-05 19:15:05 UTC
Ideally, we'd like to have a swift user for MW. One ("mediawiki") creates containers and objects and has full access to them. MW would grant access to public containers via this swift user to the second user ("webuser"). The later would just be able to read objects in the public container. SwiftFileBackend pretty much supports this. I'd like to be able to do this without "mediawiki" being an admin user if possible. This requires swifting through docs and swift code to figure out if non-admins can change ACLs on containers they own or have a certain level of access to.
(In reply to comment #0) > SwiftFileBackend pretty much supports this. I'd like to be able to do this > without "mediawiki" being an admin user if possible. This requires swifting > through docs and swift code to figure out if non-admins can change ACLs on > containers they own or have a certain level of access to. That said this isn't really a big deal (for the "mediawiki" user to have full "mw" account access) and seems like it's not avoidable anyway.
Maybe we can have users "mw:system" and "mw:rewrite".
(In reply to comment #2) > Maybe we can have users "mw:system" and "mw:rewrite". Actually, since rewrite no longer writes thumbs, we can just have "mw:system" as rewrite only needs unauthenticated reads.
This is basically done already.
