nixos-server/modules/by-name/co/constants, branch jitsi-meetnixos-config for vhack.eu servers https://vhack.euhttp://git.foss-syndicate.org/vhack.eu/nixos-server/atom?h=jitsi-meet2025-07-30T18:51:28+00:00modules/jitsi-meet: Encode the jitsi-meet user group id2025-07-30T18:51:28+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-07-30T18:51:28+00:00urn:sha1:3e048656ad3ce1c4fe10f841f0ad97b61f53c916modules/constants: Also add a user to each group, so that duplicated gids are avoided2025-04-23T10:24:31+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-04-23T10:24:31+00:00urn:sha1:3721a3474f162748c7a53f29a542a28edbc0f28amodules/stalwart-mail: Allow both nginx and stalwart-mail access to the cert2025-04-23T10:10:28+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-04-12T14:08:30+00:00urn:sha1:e48c609796a9f819e75eb05b7f4833f2d442cee7
This is needed for the http challenge (and for the potential to use
nginx as a proxy in the future.)
modules/sharkey: Init2025-04-22T19:38:47+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-04-22T19:38:47+00:00urn:sha1:e2d4d608e79237d293bc4b927c21854f8d434354modules/taskchampion-sync: Add {u,g}ids to {group,user}2025-04-11T11:30:47+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-04-11T11:30:47+00:00urn:sha1:36bf2439171be2068a620c5bc6a28113765d9da5nextcloud: init on server22025-04-07T13:30:01+00:00Silas Schöffelsils@sils.li2025-04-07T13:01:35+00:00urn:sha1:c0c8aa5fbb4ff3f6dc73c51a6333698411b7fe7emodules/mail: Avoid changing the `virtualMail` user uid2025-03-30T11:13:33+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-30T11:09:45+00:00urn:sha1:facdbe215ae2221cd31003627901803baca5db8f
We would need to set the `vmailUID` option to this value and even then
some parts of SNM would still hardcode the default of 5000.
Considering that we are in the process of phasing out SNM, this does not
seem to be a worthwhile endeavour.
modules/stalwart-mail: Assign uids and gids to the stalwart users2025-03-29T14:25:51+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-29T14:25:51+00:00urn:sha1:ddb5f85e2a518eda1645819646f59125bb33c336modules/constants: Enforce the 0 to 400 limit2025-03-29T14:24:47+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-29T14:24:47+00:00urn:sha1:b8c7040e98004c355522db339c6c8172b4f04d30modules/constants: Correctly assign each uid so that none is greater 4002025-03-29T14:22:17+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-29T14:22:17+00:00urn:sha1:086a3931a295d2ba4faa98bfe717784c26829bfb
The uid ranges from 400 upwards are reserved for things that allocate
them dynamic during runtime (like systemd). Our users would than get
clobbered, thus we avoid that range.
BREAKING CHANGE: Well, we'll need to change all uid of the files owned by the respective users.