GitLab

Update archmanweb to v1.3

See merge request archlinux/infrastructure!487

archwiki: update to 1.36.1-3

See merge request archlinux/infrastructure!488

- Drop the custom service file, use the packaged one
- Merge in the comments from the packaged config file

After=network-online.target is likely insufficient by itself.

Fixes: 104d08a1 ("archweb: Put most services after network-online.target")
Fixes: c844d0cb ("Split storage box monitoring into new text collector")

archweb: Put most services after network-online.target

See merge request archlinux/infrastructure!486

We noticed readlinks and reporead on gemini failing to connect to the
archweb database immediately after rebooting. To fix this, place them
after network-online.target. Do the same for all but one of the other
service units even though they run on timers 10-15 minutes after boot
for completeness and correctness.

The JournalHandler doesn't support flushing, anyway.

Update mirrorcheck locations

See merge request archlinux/infrastructure!483

Use wireguard for db connections to archlinux.org

Closes #177

See merge request archlinux/infrastructure!476

Fix #177

networking: Make hcloud-init.service more reliable

Closes #371

See merge request archlinux/infrastructure!474

Fix #371

Add simple playbook task for upgrading servers

We want to treat our servers as cattle; hopefully when this is fleshed
out a bit more, it can accomplish the job without too many casualties.

See merge request archlinux/infrastructure!475

This is done to avoid killing db-update and related processes.

We want to treat our servers as cattle; hopefully when this is fleshed
out a bit more, it can accomplish the job without too many casualties.

It has been applied upstream[1] and released with smartmontools 7.2[2].

[1] https://github.com/smartmontools/smartmontools/commit/61bc85ecadf9e5596b140380fed701a674e38a1b
[2] https://github.com/smartmontools/smartmontools/releases/tag/RELEASE_7_2

This reverts commit b4c97002.

Ref: archlinux/service-agreements!16

We used to set query_cache_type to 0 in the default settings but we were
also setting query_cache_size to a non-zero/non-default value, which was
in turn re-enabling the query cache. Update the configuration to reflect
the actual cache state and make sure query_cache_size is set to zero for
the "query_cache_type = 0" case.

Now that the setting controls the real state of the query cache, disable
it for bbs.archlinux.org; its hit rate is small compared to insert rate.

Default query_cache_type to 0 and innodb_file_per_table to true.