New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pretalx #2
Comments
@ngi-nix/algae will look into this, starting 2023-07-31. |
@ngi-nix/algae is progressing, packaging pretalx via poetry2nix. At the moment, it runs in a basic configuration (webserver started via shell, using an SQLite database). We'd like to introduce services soon and at that point #28 would be helpful. We haven't yet looked into a solution for components. |
A note regarding "optional dependencies": As of now, we have:
See also: ngipkgs/pkgs/pretalx/pyproject.toml Lines 12 to 16 in 4d5af8f
It looks like the preferred way to specify such dependencies is Poetry |
NixOS/nixpkgs#231684 exists and is probably further along. |
Cool, especially that you managed to package it without poetry2nix! We've merged our work in the meantime. Overall, the approach is quite similar, as would be expected. There are some differences though (handling secrets, using |
The PR to nixpkgs is awaiting further review with our contributions but in the meantime it seems we're done here |
Fix support for lists of runner labels
Pretalx is one of the leading open source tools capable of handling the full organisation of events from Call for Proposals to user feedback, and is used by many large open source events already (MozFest, FOSDEM, Pycon, NSEC, etc).
Since this project supports "components", it will need a configurable setup. Break down into separate issues as needed.
The goal here is to provide turnkey setup for self-hosting.
The text was updated successfully, but these errors were encountered: