about summary refs log tree commit diff
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
* pkgs/aszlig: Add Mutt configurationaszlig2020-08-081-1/+1
| | | | | | | | | | | | | | | | | | I've been using this configuration since years already but so far it has been residing in ~/.muttrc and I copied to new machines accordingly. The reason why I didn't add it here was because the config was too ugly and I never got so far as to properly re-do it. Unfortunately, the config is still ugly as hell, but at least we now generate it from a structured Nix format and also the IMAP/SMTP user and server infos are now retrieved via gopass instead. This also includes my small prank multipart/alternative filter, which should hopefully "encourange" recipients to disable HTML parsing/rendering. Signed-off-by: aszlig <aszlig@nix.build>
* pprofiles/workstation: Use true type VGA fontaszlig2020-08-082-6/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The DOSEMU fonts we were using so far for CP437 were bitmap fonts only and with no unicode support. Luckily there is https://int10h.org/oldschool-pc-fonts/ - which is a really cool font pack containing all the cool oldschool fonts that I remember from my childhood and still use today for creating ASCII art. Since we recently* hit the 21st century, I think it's about time that even I should start having terminals with proper Unicode support. The latter is already the case, but the glyphs just didn't display correctly. The font that I switched to (MxPlus IBM VGA 8x16) is using embededd bitmaps, so I also enabled useEmbeddedBitmaps option, so that the font still looks as crisp as the old DOSEMU font. To make sure it really is the same font, I compared screenshots of all the CP437 characters with the new font and they match the old font 1:1. I also removed the liberation_ttf font, since it's already included by the default NixOS font configuration. * -> Your mileage may vary, but hey, the 90ies were yesterday, right? Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Replace weechat with irssidevhell2020-08-071-1/+1
| | | | | | I'm really not digging the fact that weechat _constantly_ changes stuff in it's config directory. Makes keeping it under version control a pain in the ass.
* workstation/packages: Add "entr"aszlig2020-07-281-0/+1
| | | | | | | | | | | | | I regularily keep things in nix-env to see whether I keep using them and "entry" is one of the little tools I ended up using quite regularily. The program monitors a set of files via inotify and runs a command whenever one or more of them change, which makes it quite useful for a "change code, compile, run" cycle. Upstream URL: https://eradman.com/entrproject/ Signed-off-by: aszlig <aszlig@nix.build>
* Revert "profiles/base: Allow mpd to access pulseaudio"devhell2020-07-271-1/+0
| | | | | | Whatever the case, I don't want this anymore. This reverts commit 04bbb9966ba29fca3026a606adaa42a8a415523b.
* profiles/packages: Add ugrepdevhell2020-07-251-0/+1
| | | | This seems to be useful.
* workstation: Disable pull.rebase in Git configaszlig2020-07-161-0/+1
| | | | | | | | | | | | | | | | | | | | From the release notes of Git version 2.27.0: * "git pull" issues a warning message until the pull.rebase configuration variable is explicitly given, which some existing users may find annoying---those who prefer not to rebase need to set the variable to false to squelch the warning. This is exactly the warning which is annoying me all the time now, so in order to get rid of it, let's explicitly set the default behaviour (which is doing a recursive merge). Just to be sure that I really want the default behaviour, I analysed my shell history for invocations of "git pull" and only around 20% of the invocations were with --rebase, 14% were with an explicit URL (but no rebase) and the rest were recursive merges. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Add oneshotdevhell2020-07-151-0/+1
| | | | This seems useful.
* profiles/packages: Add iconsdevhell2020-07-101-1/+4
| | | | Stuff like `virt-manager` has broken buttons.
* profiles/base: Enable Nix experimental featuresaszlig2020-06-231-0/+1
| | | | | | | | I've had this in my configuration.nix for a while and since I got used to it, I think it's a good idea to enable both Nix Flakes and the "nix" command by default for all my machines. Signed-off-by: aszlig <aszlig@nix.build>
* modules/user/profpatsch/bitlbee: fix ConfigDirProfpatsch2020-06-191-1/+1
|
* modules/profpatsch/weechat: add wrapExecStartProfpatsch2020-06-191-4/+14
|
* modules/user/profpatsch/services: add bitlbeeProfpatsch2020-06-192-0/+90
| | | | Also add the service to legosi so I can use it from the weechat user.
* profiles/packages: Remove virtinst overridedevhell2020-06-181-9/+0
| | | | I'm fairly certain this isn't needed anymore.
* profiles/base: Remove hardware.u2fdevhell2020-06-161-1/+0
| | | | | | | According to [1], `udev` has gained native support for FIDO security tokens, and subsequently has been removed upstream. [1]: 89c3e73dad0970b26183e415555fb0379ba33e7a
* Revert "profiles/packages: Remove p7zip"devhell2020-06-161-0/+1
| | | | | | | As already stated otherwise in this log, it's back, so reverting the removal. This reverts commit 54b3f8ac7da02738be6919d05ae12d5c14796e3f.
* profiles/workstation: Revert replacing p7zipaszlig2020-06-151-1/+1
| | | | | | | | | | | | This reverts commit 64fdbcc7e0949a3d3bf1cee3361d5ebe5c56cc4c. It seems that there is now[1] a maintained version of p7zip and since I didn't get used to unar so far, I take this opportunity to switch back to p7zip. [1]: https://github.com/NixOS/nixpkgs/pull/90140 Signed-off-by: aszlig <aszlig@nix.build>
* modules/user/profpatsch: add programs/weechat moduleProfpatsch2020-06-152-0/+120
|
* profiles/packages: Add zstddevhell2020-06-091-0/+1
|
* core/tests: Fix eval of wireguard tests for realaszlig2020-06-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | I even mentioned the full names of the test attributes in bc4203d221c87a0622d089aaa61884f86d40fd44: tests.wireguard.wireguard-basic-linux-5_4 tests.wireguard.wireguard-basic-linux-latest tests.wireguard.wireguard-generated-linux-5_4 tests.wireguard.wireguard-generated-linux-latest tests.wireguard.wireguard-namespaces-linux-5_4 tests.wireguard.wireguard-namespaces-linux-latest tests.wireguard.wireguard-wg-quick-linux-5_4 tests.wireguard.wireguard-wg-quick-linux-latest So I forgot about the additional "wireguard-" prefix, so Hydra fails to evaluate again: in job 'tests.nixos.wireguard.basic-linux-5_4': evaluation aborted with the following error message: 'cannot find attribute `nixos.wireguard.basic-linux-5_4'' Signed-off-by: aszlig <aszlig@nix.build>
* core/tests: Add missing wireguard attr suffixesaszlig2020-06-031-4/+8
| | | | | | | | | | | | | | | | | | | | | | Commit 89c3cda819da5dc32e4a29ff8f2aad118bde64c7 changed the wireguard attributes to use nested attributes because it was changed upstream. However what the commit has missed is that the attributes are not just plain attributes but come with a kernel version suffix, for example like this: tests.wireguard.wireguard-basic-linux-5_4 tests.wireguard.wireguard-basic-linux-latest tests.wireguard.wireguard-generated-linux-5_4 tests.wireguard.wireguard-generated-linux-latest tests.wireguard.wireguard-namespaces-linux-5_4 tests.wireguard.wireguard-namespaces-linux-latest tests.wireguard.wireguard-wg-quick-linux-5_4 tests.wireguard.wireguard-wg-quick-linux-latest Adding the "-linux-${version}" suffix should fix evaluation. Signed-off-by: aszlig <aszlig@nix.build>
* core/tests: Fix attribute paths for wireguardaszlig2020-06-031-3/+6
| | | | | | | | | | | | | | | | | | A few days ago, the wireguard tests were consolidated[1] into a single attribute with various subattributes, similar to how the virtualbox tests and many other tests are structured. I fixed the attributes and also added the wg-quick attribute that was also introduced in the meantime[2]. This should fix the evaluation errors occuring whenever a channel contains a machine configuration with wireguard enabled. [1]: https://github.com/NixOS/nixpkgs/commit/41bd6d2614749d12ce5ded3e991555b56ea6b2dc [2]: https://github.com/NixOS/nixpkgs/commit/abf60791e2bd274d39e0f18def46795798f9aefd Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* modules/base: Fix bashdevhell2020-05-301-1/+0
| | | | I shouldn't be working today I think.
* modules/{base,packages}: Fix screendevhell2020-05-302-3/+1
| | | | Duh.
* modules/{base,packages}: Use programs.* wrapperdevhell2020-05-302-15/+22
| | | | | Replacing the simple inclusion of some programs in packages with their respective programs.* equivalent.
* modules/{packages,services}: Remove keybasedevhell2020-05-262-2/+0
| | | | Aquired by Zoom, no thanks.
* pkgs/aszlig/xournal: Switch to xournal++aszlig2020-05-211-1/+1
| | | | | | | | | | | | | The patch I added to xournal was for keeping the aspect ratio when annotating PDFs with images. However, looking at xournal++ the aspect ratio is kept by default when resizing via corners so the patch is not needed. Since I don't really care a lot whether it's xournal or xournal++ and as long as it does the very little things I intend to use it for, I don't mind if it has too many features for my taste. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Add signal-desktopdevhell2020-05-161-1/+2
| | | | Knew I forgot something in the last clean-up.
* devhell-wide: Remove unnecessary packagesdevhell2020-05-141-2/+0
| | | | Still a continuation of some housekeeping.
* zsh: Fix XTerm-specific shell initialisationaszlig2020-05-081-1/+1
| | | | | | | | | | | | | In 7faaaab0af1e30bdfb72eca02abdfe92efefe4e0, I've changed the TERM variable to contain "xterm-256color". However, in our shell initialisation, we check whether $TERM is "xterm" rather than whether $TERM *starts* with xterm. Doing the latter fixes title setting and home/end keys in Vi normal mode. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Set XTerm colours to 256aszlig2020-05-071-0/+1
| | | | | | | | | | | So far I've been fine with just everything using 16 colours, but since I'm even using 256 colours in my own ASCII art spriting engine I think I can safely enter the 90ies and get some more colours. Of course, the XTerm version I'm using is already supporting 256 colors, it's just that the terminfo entry doesn't say so. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Replace p7zip with unaraszlig2020-05-061-1/+1
| | | | | | | | | | | | | | A while ago, p7zip has been marked as insecure[1], and while I didn't use p7zip for any real archives, I used it for unrelated things like executables and ISO9660 images and of course occasionally also 7z files. While I haven't done extensive testing with unar, it does seem to have a similar feature set when it comes to non-archive formats and also has support for 7z archives as well. [1]: https://github.com/NixOS/nixpkgs/commit/aa80b4780d849a00d86c28d6b3c Signed-off-by: aszlig <aszlig@nix.build>
* core/tests: Fix attribute for Docker containersaszlig2020-05-051-2/+2
| | | | | | | | | | The option has been renamed[1] from just "docker-containers" to "virtualisation.oci-containers.containers", so our checks no longer evaluate. [1]: https://github.com/NixOS/nixpkgs/commit/2f7747526cc80844a506c4aa147 Signed-off-by: aszlig <aszlig@nix.build>
* profiles/packages: Remove p7zipdevhell2020-05-031-1/+0
| | | | | Unfortunately, development has seemingly ceased and has been marked as insecure in aa80b4780d849a00d86c28d6b3c78a777dd02e9a.
* modules/services/drawpile: open TCP not UDPProfpatsch2020-05-021-1/+1
|
* modules: add services/drawpileProfpatsch2020-05-022-0/+72
| | | | Headless server for the drawpile shared drawing application.
* modules/tests: Fix eval of dokuwikidevhell2020-04-241-1/+1
| | | | | | | With the merge of [1], the `.enable` check for `config.services.dokuwiki` has been removed. [1]: https://github.com/NixOS/nixpkgs/pull/83769
* treewide: Remove hardware.opengl.s3tcSupportdevhell2020-04-233-3/+0
| | | | | | | This option has been dropped upstream in 4732f59226a21b01d630c7ef4fb884bbfbe7dc83 Cc: @aszlig
* modules/services: Fix lightdm mini greeter borderdevhell2020-04-181-1/+3
| | | | | | | Since the latest update to `0.4.0` `lightdm` has added some more fine-grained options to how the greeter behaves. In this case it added a border around the password input box which doesn't look nice, so I'm making it vanish here.
* core/tests: Rename references to "nesting"aszlig2020-04-151-5/+4
| | | | | | | | | | | The nesting.clone and nesting.children options were renamed[1] upstream and they're now contained in one single submodule option, which means that for our tests we only need to check for config.specialisation instead of nesting.clone and nesting.children separately. [1]: https://github.com/NixOS/nixpkgs/commit/ec2d28e3233c4c04fe6afe13e82 Signed-off-by: aszlig <aszlig@nix.build>
* core/tests: Remove check on graphite.pageraszlig2020-03-231-1/+1
| | | | | | | | | | | | All of the NixOS options in services.graphite.pager have been removed in 37ffa6ea51f3a3d7e43736b9a5ce3c149dd9d1ee, but since we're using the "enable" option to check whether we need to run tests, we'll get an eval error. Removing the check fixes the evaluation error. Signed-off-by: aszlig <aszlig@nix.build> Reported-by: @devhell
* profiles/base: Switch back to latest kerneldevhell2020-03-041-1/+1
| | | | | With VirtualBox gone, I should be able to use the latest Linux kernel again. Yippie!
* profiles/services: Disable virtualboxdevhell2020-02-291-1/+1
| | | | | | | | | I've been trying to get away from VirtualBox for quite some time now. unfortunately work has been preventing me from ditching it. I've been doing some tests with virt-manager and, for now, I think it might be an okay replacement. The only problem is that I've not found a way to similarly export/import VMs in a convenient fashion which VirtualBox offers.
* profiles/base: Remove nerdfontsdevhell2020-02-261-1/+0
| | | | | Having added nerdfonts was a bad idea because it's 5G apparently. Let's not do this to aszlig's hydra.
* profiles/base: Add nerdfonts and cozettedevhell2020-02-251-0/+2
|
* devhell: Replace chromium with bravedevhell2020-02-221-1/+1
| | | | | | | | | I'm quite tired and bored of things like [1]. I can't find evidence that Brave has implemented this, so Brave will replace Chromium. [1]: https://www.chromestatus.com/feature/4733392803332096
* machines/{eir,gunnr}: Switch pamixer to profiledevhell2020-02-111-0/+1
| | | | Small but still valid step towards more de-DRYing.
* profiles/base: Temporarily pin Kernel versiondevhell2020-02-101-1/+1
| | | | | VBox doesn't build with the newest Kernel. So, best to stick with the old 5.4 for now.
* core/tests: Fix option check for buildkite-agentsaszlig2020-02-101-1/+1
| | | | | | | | | Another thing I missed in ffa7a45ba0aa27c926472e23587423bc07a6db53 is that not only the module got renamed, but its interface has changed as well and instead of an "enable" option, it's now just an attribute set of submodules and the service(s) are enabled whenever it's non-empty. Signed-off-by: aszlig <aszlig@nix.build>
* core/tests: Rename module for buildkite-agentaszlig2020-02-101-2/+2
| | | | | | | | | | | | The buildkite-agent module, NixOS test and option got renamed[1] to its plural form, also supporting multiple agents. While none of our machines are using the module, we nevertheless need to fix the module option attribute so that our channels will evaluate. [1]: https://github.com/NixOS/nixpkgs/commit/f003810989c58746db9ea52f623 Signed-off-by: aszlig <aszlig@nix.build>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-11 15:12:31 +0000