Install OOM configuration

See merge request !491

Jan Alexander Steffens (heftig) authored 3 years ago and Kristian Klausen committed 3 years ago

- When loki hits 5.5G RSS, aggressively reclaim its memory. This puts
  it under memory pressure.
- When loki hits 6G RSS, invoke the kernel OOM killer.
- When loki is under severe memory pressure, have systemd-oomd kill it.

Jan Alexander Steffens (heftig) authored 3 years ago and Kristian Klausen committed 3 years ago

- Allow killing of any cgroup if swap is about to run out. When swap is
  at least 90% full, oomd will kill a cgroup, tending to kill the cgroup
  with the highest swap usage.
- Allow killing cgroups of logged in users under severe memory pressure.
  When a cgroup is stalled waiting for memory at least 60% of the time,
  for at least 30 seconds, oomd will attempt to kill it or one of its
  descendant cgroups.

This partially reverts commit c3d00264.

The smartd changes are not ready to land yet and were included in the
above commit by accident.

phrik has a polkit rule for demize to restart phrik

Also adjust indentation and make the uploaded files owned by nobody.

Some people love to do 48 req/s to our tracker which causes ~100% cpu.
For now we allow 5req/sec with a burst of 10 requests.

Mention postgresql/gitlab/mariadb backups

See merge request !299

Jelle van der Waa authored 4 years ago and Sven-Hendrik Haase committed 3 years ago

Document how we backup our databases/gitlab instances.

keycloak: Enable account registation (fixes #39)

Closes #39

See merge request !15

Add Keycloak terms and conditions

See merge request !482

Ref: service-agreements!16

Update archmanweb to v1.3

See merge request !487

archwiki: update to 1.36.1-3

See merge request !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 !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.