Repository navigation
make logs public? #174
Description
Activity
The only opposition I have to making them public is if something secret does ever end up part of the builds and that is subsequently logged.
Logs would now need redaction to make public due to the Fastly purging changes.
Since they now need redaction, I'm going to close this, as I don't think it's worth the complexity.
Sure, we have more of the core team with access to the docsbuild server to check the logs and to Sentry, so it's less of a problem. We can add more of the core team if they'd like access.
Reacted by Stan Ulbrych
Following #173 (comment)
Pinging @cegerhardson and @ewdurbin.
Question is: what about making the /var/log/docsbuild/docsbuild.log public by either uploading it somewhere else, or just having it accessible through https://docs.python.org as the server is already a webserver.
There's no secret in there.