about summary refs log tree commit diff stats
path: root/modules (follow)
Commit message (Collapse)AuthorAge
* modules/matrix: Remove failing postgresql post-start code HEAD mainBenedikt Peetz21 hours
| | | | This code stops postgrsql from starting.
* modules/anubis: Make sure ngnix is actually enabledBenedikt Peetz23 hours
|
* modules/mail: Apply migrations and set initial stateVersionBenedikt Peetz24 hours
| | | | | The server is already migrated, as such we should also try to apply this update in the very near future.
* modules/sharkey: Use the up-streamed nixpkgs moduleBenedikt Peetz24 hours
| | | | This works now, as we updated to 25.11.
* modules/rust-motd: Avoid using the deprecated `runCommandNoCCLocal`Benedikt Peetz24 hours
|
* modules/stalwart-mail: Use the nixpkgs' starwart packageBenedikt Peetz24 hours
| | | | Ours is hopelessly broken and right now also pointless.
* modules/nextcloud: Update to nextcloud 32Benedikt Peetz24 hours
|
* modules/anubis: Introduce and setupBenedikt Peetz24 hours
| | | | | | | This should hopefully reduce the workload applied to our servers. Notably, `cgit` is not yet behind it, as it requires more, considering that it is a fgi application.
* modules/sharky: Add stup option for `services.melisearch.settings`Benedikt Peetz2025-08-04
| | | | | We use the unstable module that sets this options (behind a `lib.mkIf false`). They are not needed, but the module system needs them to exist.
* Revert "{modules,test}/jitsi-meet: Init"Benedikt Peetz2025-08-04
| | | | | | | This reverts commit 8040a61b373621e3e8a3684aecbb5cbf66d895c7. Jitsi did not work, and I think that it will need a better approach than this (i.e., updates to the NixOS module).
* modules/grocy: Init grocy-newBenedikt Peetz2025-08-03
|
* {modules,test}/jitsi-meet: InitBenedikt Peetz2025-07-29
|
* modules/sharkey: Drop pointless dependency on `network-online.target`Benedikt Peetz2025-07-13
| | | | | Sharkey can start without network and therefore does not need this dependency.
* {modules,pkgs}/sharkey: Use the sharkey package and module from nixpkgsBenedikt Peetz2025-07-13
| | | | Sharkey was package in nixpkgs.
* modules/users: Apply new formattingBenedikt Peetz2025-07-06
|
* modules/rust-motd: Add new `cg_stats` and `load_avg` sectionsBenedikt Peetz2025-06-23
|
* modules/rust-motd: Use correct name for `fail_2_ban` sectionBenedikt Peetz2025-06-23
| | | | This was change in one of the last releases.
* modules/rust-motd: Remove pointless ssl certificate sectionBenedikt Peetz2025-06-23
| | | | | The certificates are auto-renewed. As such, we don't need to know, when they expire.
* modules/rust-motd: Generate the banner ahead of timeBenedikt Peetz2025-06-23
|
* modules/users: change sils sshkeySilas Schöffel2025-06-23
| | | | My nitrokey ceased its cooperation with my setup :(
* modules/redlib: Remove old `libreddit` aliasBenedikt Peetz2025-06-07
|
* modules/git-back: Init with the out-of-tree backBenedikt Peetz2025-06-07
|
* pkgs/stalwart-mail: Update to nixos 25.05Benedikt Peetz2025-06-06
| | | | | Now the stalwart-mail package is by default free. As such, we could drop the respective patches.
* modules/atuin-sync: InitBenedikt Peetz2025-05-05
|
* modules/matrix: Provide postgresql with a correct sql statementBenedikt Peetz2025-05-04
|
* modules/nextcloud: add calendar, contacts, tasks appsSilas Schöffel2025-05-04
|
* pkgs/taskchampion-sync: Put the sync server behind a ngnix proxyBenedikt Peetz2025-04-28
| | | | | | I realized, that the new taskchampion-sync-server uses a http api (instead of the custom protocol of taskserver). As such, we obviously want to put it behind a ngnix reverse proxy.
* modules/sharkey: Add required `@chown` syscall group to allow listBenedikt Peetz2025-04-25
| | | | The `~@priviledged` needed to go, as `@chown` is part of this group.
* modules/sharkey: Ensure, that it can access the host's CPUsBenedikt Peetz2025-04-24
| | | | This is, for some reason, needed for image uploads to sharkey.
* modules/system-info: Provide a nice warning message, if a port is not yet ↵Benedikt Peetz2025-04-24
| | | | registered
* modules/matrix: Use the typed NixOS for user and db creationBenedikt Peetz2025-04-24
| | | | | | Note, that I have no way to test if this is actually going to work (no tests for matrix). But, I assume that it is not going to pose problems, as we are not migrating the db and these options won't remove state.
* modules/matrix: Group `vhack` attr keys togetherBenedikt Peetz2025-04-24
|
* modules/mastodon: Group `vhack` keys togetherBenedikt Peetz2025-04-24
|
* modules/taskchampion: Make its data directory owned by taskchampion userBenedikt Peetz2025-04-23
|
* modules/stalwart-mail: Add recommended proxy settings for stalwarts-proxyBenedikt Peetz2025-04-23
| | | | This includes setting things, like setting the `X-Forwarded-For` header.
* modules/constants: Also add a user to each group, so that duplicated gids ↵Benedikt Peetz2025-04-23
| | | | are avoided
* modules/stalwart-mail: Don't restart the systemd serviceBenedikt Peetz2025-04-23
| | | | | | Restarting might be useful, if stalwart is actually _running_ in prod, but currently the constant restart makes it very difficult to debug (or even stop) the service.
* modules/stalwart-mail: Enable the http self-service interfaceBenedikt Peetz2025-04-23
|
* modules/nginx: Set the "acme" group as group of the "acme" userBenedikt Peetz2025-04-23
| | | | | For some reason, this is not done already. Setting this prevents an assertion being thrown, that the "acme" user does not have a group.
* modules/stalwart-mail: Allow both nginx and stalwart-mail access to the certBenedikt Peetz2025-04-23
| | | | | This is needed for the http challenge (and for the potential to use nginx as a proxy in the future.)
* modules/stalwart-mail: Explicitly list out valid password hashesBenedikt Peetz2025-04-23
| | | | | | If a password hash does not match stalwart's know ones, it will just treat it as plaintext. This is obviously very bad, and should be avoided.
* modules/stalwart-mail: Make `cfg.principals` nullableBenedikt Peetz2025-04-23
| | | | This makes it possible to use the internal storage
* modules/stalwart-mail: Use correct group name for `redis-stalwart-mail`Benedikt Peetz2025-04-23
|
* modules/sharkey: InitBenedikt Peetz2025-04-22
|
* modules/system-info: Register taskchampion portBenedikt Peetz2025-04-11
|
* modules/taskchampion-sync: Persist data directoryBenedikt Peetz2025-04-11
|
* modules/taskchampion-sync: Add {u,g}ids to {group,user}Benedikt Peetz2025-04-11
|
* {modules,test}/taskchampion-sync: InitBenedikt Peetz2025-04-11
|
* nextcloud: init on server2Silas Schöffel2025-04-07
|
* {hosts/server2,modules/mail}: Re-active the old mail serverBenedikt Peetz2025-03-30
| | | | | | | | | | Running two mail-servers on one system is a total /mess/. Both try to bind to the same ports, the old stack consists of **5** different systemd services whilst stalwart-mail's systemd service simply refuses to stop, etc. I'm confident that it can work, but it would probably be best to deploy the new mail-server on server3.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2025-12-19 16:36:01 +0000