hacc/haccfiles
8
0
Fork 1
Code Issues 1 Pull requests Projects Releases Wiki Activity
haccfiles/pkgs/default.nix

34 lines
751 B
Nix
Raw Normal View History

less verbose container definitions move some options (the nopersist & container profiles + allowUnfree packages) into the evalConfig used for containers, so we don't have to repeat ourselves as much. also removed some no-longer-needed specialArgs. also made thelounge work with nopersist, which for some reason it didn't use before.
2023-09-27 21:24:23 +00:00
{ sources, ... }@args:
Initial Commit
2020-11-27 20:56:20 +00:00
let
pkgs: pass nixpkgs config properly see https://gitlab.com/hexchen/nixfiles/-/commit/cee4094d91f7e928df54814902bb99366e4d4da5 for details of upstream changes
2021-01-11 00:11:40 +00:00
pkgs = import sources.nixpkgs args;
keep using the old uffd's pythonPackages, lol
2023-09-27 15:14:05 +00:00
oldstable = import sources.nixpkgs-oldstable args;
mattermost: 8.1.10 → 9.5.1 This jumps Mattermost ESR Versions (see [1] for their release cycle). The new version makes use of Go's workspace feature, which unfortunately the buildGoModule function does not (yet?) support [2], and unfortunately this breaks the previous build process for mattermost. Further, the new release also makes use of private modules only included in the (non-free) enterprise version of mattermost which makes it impossible to build in the usual way even outside of nixpkgs's build abstractions [3]. Both issues can be solved by using Go 1.22, which has added support for vendoring when using workspaces, and instructing it to ignore errors with the -e flag. This requires overriding the go-modules derivation's buildPhase. Finally, this now also build the commands/mmctl subpackage, which contains a cli utility to administrate mattermost. This currently has its own nixpkgs package for no reason i can see at all (it also has a version mismatch between nixpkgs's mattermost and nixpkgs's mmctl). [1] https://docs.mattermost.com/upgrade/extended-support-release.html [2] https://github.com/NixOS/nixpkgs/issues/203039 [3] https://github.com/mattermost/mattermost/issues/26221
2024-02-21 16:38:40 +00:00
unstable = import sources.nixpkgs-unstable args;
Initial Commit
2020-11-27 20:56:20 +00:00
complete restructure of haccfiles here be winkekatzen
2021-01-10 23:53:41 +00:00
callPackage = pkgs.lib.callPackageWith (pkgs // newpkgs);
peertube: init from immae source: https://git.immae.eu/?p=perso/Immae/Config/Nix.git;a=tree;f=pkgs/webapps/peertube;hb=b639cc33725fed62988b616909843bea7f7aebe3
2020-11-30 18:30:24 +00:00
Initial Commit
2020-11-27 20:56:20 +00:00
newpkgs = {
pkgs: init bitfocus companion for streamdeck
2021-08-28 14:30:02 +00:00
mattermost: 8.1.10 → 9.5.1 This jumps Mattermost ESR Versions (see [1] for their release cycle). The new version makes use of Go's workspace feature, which unfortunately the buildGoModule function does not (yet?) support [2], and unfortunately this breaks the previous build process for mattermost. Further, the new release also makes use of private modules only included in the (non-free) enterprise version of mattermost which makes it impossible to build in the usual way even outside of nixpkgs's build abstractions [3]. Both issues can be solved by using Go 1.22, which has added support for vendoring when using workspaces, and instructing it to ignore errors with the -e flag. This requires overriding the go-modules derivation's buildPhase. Finally, this now also build the commands/mmctl subpackage, which contains a cli utility to administrate mattermost. This currently has its own nixpkgs package for no reason i can see at all (it also has a version mismatch between nixpkgs's mattermost and nixpkgs's mmctl). [1] https://docs.mattermost.com/upgrade/extended-support-release.html [2] https://github.com/NixOS/nixpkgs/issues/203039 [3] https://github.com/mattermost/mattermost/issues/26221
2024-02-21 16:38:40 +00:00
mattermost = callPackage ./mattermost.nix {
buildGoModule = unstable.buildGo122Module;
};
hainich: hacky version of thelounge as webchat Intended for KontraIAA; requirements were that it should be a simple and non-confusing as possible. I tried both KiwiIRC and thelounge, and found both horrible to package (a fact not helped by the somewhat opaque structure of nixpkgs.nodePackages, which does contain a version of thelounge but will apparently ignore overrides of the src attribute). Instead, this now contains a very hacky version of thelounge, which merely takes the already-built version from nixpkgs and glues some extra css to it which hides potentially confusing fields. Things hidden on the "connect" screen: - the "name" field (since thelounge offers "nick" "name" and "realname" by default, which seems too much for something embedded on a website) - the "I have a password" checkbox Things hidden on the general view: - the button to open the side panel (the panel itself is not hidden, and will appear by itself on wider layouts), so that users will only see that one channel - the "channel options" menu (which includes a "leave channel" option which would effectively break the webchat) Things not addressed: - thelounge has autocompletion for /join /leave, etc. Do we want to disable that as well? - It would probably useful to suppress all the "x joined the channel" messages. Thelounge supports this, but apparently doesn't support setting it as default? Misc: - for now, users will be connected to #thelounge on libera.chat, which appears to be okay with being used as an experimental channel - I allowed prefetching link previews, but only on the server's side (i.e. users' browsers won't fetch content from arbitrary sites) - not yet tested on hainich, but should work (tested in a NixOS container) - currently assumes a "webchat.voc.hacc.space" domain (I think we had a voc domain? but I forgot where it is …)
2021-08-05 17:11:43 +00:00
bundle forgejo @ v7.0.2 this bundles the current package recipe of forgejo in nixpkgs-unstable. Implies updating forgejo, since nixpkgs-stable is still on 1.20.6 (v6 in the new version scheme). This'll mean we have to manually update it same as with mattermost, and can potentially also help with upstream changes. If we get tired of that, we can always decide to just use the nixpkgs-unstable version directly.
2024-05-16 17:06:15 +00:00
forgejo = callPackage ./forgejo {
buildGoModule = unstable.buildGo122Module;
};
init tracktrain
2023-01-22 01:25:07 +00:00
tracktrain = import sources.tracktrain {
nixpkgs = pkgs;
update inputs this now no longer needs to be built with allow_broken; tracktrain's packaging now includes an override to remove the marked-broken state.
2023-07-02 21:31:25 +00:00
compiler = "default";
init tracktrain
2023-01-22 01:25:07 +00:00
};
keep using the old uffd's pythonPackages, lol
2023-09-27 15:14:05 +00:00
uffd = oldstable.callPackage ./uffd { };
feat: new SSO!!!! :tada:
2022-04-30 20:43:12 +00:00
keep using the old uffd's pythonPackages, lol
2023-09-27 15:14:05 +00:00
inherit (oldstable) uwsgi flask;
common: *licks the infra* Since Lix is now in nixpkgs-unstable-small, I think it's a good time to use it. This does mean that we now pull in our nix implementation from an unstable channel, but overall I'm more confident in the Lix team's ability to not break things than I am in the Nix team's ability to backport (& then actually release) security updates. (once Lix is on a stable channel, we can switch back to using it from there)
2024-05-13 12:39:51 +00:00
# TODO: once on nixos 24.05, remove this inherit
inherit (unstable) lix;
Initial Commit
2020-11-27 20:56:20 +00:00
};
sources: switch to upstream this involves moving the blackmagic package and module from hexchen's nixpkgs fork into this repo directly.
2021-01-27 05:24:12 +00:00
in pkgs.extend(_: _: newpkgs)
Reference in a new issue Copy permalink