| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Some sites that had non-ASCII characters rendered weirdly because our
NGINX configuration was not returning a default charset and so rendering
was being left up to browser/standards defaults.
This change adds a new config file to /etc/nginx/conf.d/ which forces
responses to be interpreted as/transformed to UTF-8.
|
|
|
|
|
|
| |
At present we get plenty of unactionable, flapping alarms. So far, they
have shown us nothing of value. Raise the time consecutive errors need
to be seen before we alert.
|
|
|
|
|
| |
See
https://github.com/python-discord/infra/pull/524#issuecomment-2323385510.
|
| |
|
|
|
|
|
| |
Also ignore the promethues-postgres-exporter which is a submodule and is
not subject to our lint rules
|
| |
|
| |
|
|
|
|
| |
Closes #474.
|
| |
|
|
|
|
|
|
| |
| datasource | package | from | to |
| ---------- | --------------- | ------ | ------ |
| pypi | mkdocs-material | 9.5.33 | 9.5.34 |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This performs a syntax check instead of attempting a load to prevent
unresolvable tags (i.e. Ansible's `!vault`) from kicking up errors.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Include a missing PreDown task to remove the local routes we add as well
as including all hosts in the inventory instead of just netcup hosts.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This also moves custom plugins into the `roles/munin/templates/plugins`
directory, which should hopefully be easier to maintain than the
existing inline dictionary. The only issue is that now it is a bit
harder to deal with the filepaths.
This change has already been deployed.
|
|
|
|
|
|
| |
| datasource | package | from | to |
| ---------- | ------- | ----- | ----- |
| pypi | ruff | 0.6.2 | 0.6.3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Already deployed on lovelace. I was going to leave out script deployment
and just write it inline, but YAML folding of long lines (and
unreadability of 200 column-wide AWk scripts, to be honest) made it a
bit bad.
The e-mail for DevOps cron failure reports is updated to include `+cron`
to allow for client-side filtering, if necessary.
To test: `ssh -L localhost:9090:localhost:9090 lovelace.box.pydis.wtf`,
then check out the `dovecot_` variables in the UI.
We might want to further check out Dovecot's built-in statistics
support, see https://doc.dovecot.org/2.3/configuration_manual/stats/.
|
|
|
|
| |
As suggested by Joe.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Directories under /var/vmail are no longer all owned by `vmail`, but
instead `$ldap_uid:vmail`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A spectre is haunting Python Discord -- the spectre of proprietary mail
filtering programs. All the Powers of Big Mail have entered into a holy
alliance to exorcise this spectre: Outlook and GMail, Yahoo and Zoho,
AOL adn iCloud.
Where is the open protocol in opposition that has not been decried as
unprofessional, free and open source by its opponents in power? Where is
the Opposition that has not hurled back the branding reproach of
Internet Standards, against the more advanced opposition protocols, as
well as against its reactionary adversaries?
Two things result from this fact.
I. Sieve is already standardized as a protocol via the IETF.
II. It is high time that Python Discord users should openly, in the face
of the TLS-encrypted internet, filter their notifications, their love
letters, their mailing lists, and meet this nursery tale of the Spectre
of ManageSieve with a Manifesto of Python Discord Devops itself.
To this end, ManageSieve users of various nationalities have assembled
on jitsi.pydis.wtf, and sketched the following commit, to be published
on the lovelace Python Discord e-mail service.
|
| |
|
| |
|
| |
|
| |
|