Create a MW-Vagrant role for Sentry Extension:Sentry.
Description
Details
Event Timeline
Change 181606 had a related patch set uploaded (by Gergő Tisza):
[WIP] Add Vagrant role for Sentry (server MW extension)
Change 181779 had a related patch set uploaded (by Gergő Tisza):
Rename $wgSentryEndpoint to $wgSentryDsn to better match the docs
Change 181779 merged by jenkins-bot:
Rename $wgSentryEndpoint to $wgSentryDsn to better match the docs
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?
Change 189184 had a related patch set uploaded (by Gergő Tisza):
Remove system user/group options from Sentry role
Change 189184 abandoned by Gergő Tisza:
Remove system user/group options from Sentry role
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.