- Mentioned In
- rESNT0d7fa6f0a227: Rename $wgSentryEndpoint to $wgSentryDsn to better match the docs
rMEXTc9477b64d544: Updated mediawiki/extensions Project: mediawiki/extensions/Sentry…
rMWVA9cd92d68af32: Add Vagrant role for Sentry (server + MW extension)
T84956: Create basic puppet role for Sentry
- Mentioned Here
- T90773: Fix log directory permissions in Sentry vagrant role
I am running into various permissions-related trouble, e.g. ImproperlyConfigured: Could not write to directory: /vagrant/logs/sentry.mail.log.
Vagrant does not seem to play nice with the concept of separate user/group per application.
@dduvall, which direction would you prefer, making sentry use www-data or making directory settings more permissive?
I would make it all run as www-data personally. This is an unprivileged system user allocated for Apache but is more generally used in the WMF cluster as the user that runs MediaWiki code. Granular control of file permissions in Vagrant for host mounted directories are fragile. Almost ever time we try to change them we break something.
If all that's left is switching to www-data, I think it should be a new dedicated task and this one should be closed. There's a vagrant role for sentry now, everything from this point on is specific improvements/bugfixes.