A packaging of Zulip server for NixOS
  • Nix 95.3%
  • Python 4.7%
Find a file
sinavir 56a49ce3f7
All checks were successful
/ ci (x86_64-linux) (pull_request) Successful in 23m56s
/ ci (x86_64-linux) (push) Successful in 20m24s
fix(postgresql): custom sql is no longer needed
The sql setup statements are now part of zulip first migration
2026-04-01 11:36:21 +02:00
.forgejo/workflows add forgejo actions 2025-08-29 18:02:30 -07:00
LICENSES zulip-prometheus-exporter: init at 0.1.0 2025-08-06 17:16:15 -07:00
nix fix(postgresql): custom sql is no longer needed 2026-04-01 11:36:21 +02:00
.envrc pluralize attributes 2025-08-29 16:48:53 -07:00
.gitignore add nixos test for zulip 2025-08-06 21:21:34 -07:00
engage.toml feat(engage.toml): run all the tests in the CI 2025-12-30 13:59:40 +01:00
README.md feat(lappverk): init tooling 2026-04-01 11:36:21 +02:00
REUSE.toml start the project 2025-08-06 13:35:47 -07:00
shell.nix feat(shell): add shell.nix 2025-12-01 10:56:51 +01:00
treefmt.toml start the project 2025-08-06 13:35:47 -07:00

nix-zulip

This repository packages Zulip for Nix and NixOS.

Updating

  1. Bump the version in the zulip-server package and the other dependencies (you can use nix-update for that)

  2. Check if any dependency changed from the upstream pyproject.toml

  3. [Optional] Compare version requirements from uv.lock and

  4. Create a new patchset using lappverk. A typical workflow looks like (for 11.2 -> 11.4 update):

    pushd nix/packages/zulip-server
    lappverk checkout @/patches-11.2
    lappverk init patch-series @/patches-11.4 --base 11.4
    pushd $(lappverk checkout nix/packages/zulip-server/patches-11.4)
    git cherry-pick lappverk/base/patches-11.2..lappverk/patches-11.2
    
    # resolve (or --skip) any conflicts that come up, as per usual...
    # then, once the whole series has been cherry-picked
    
    lappverk export @/patches-11.4
    popd
    popd
    

    This workflow is encoded in the lappverk-start-rebase OLD_TAG NEW_TAG and lappverk-finish-rebase bash functions exported by the shell.

  5. Run the tests with engage