about summary refs log tree commit diff
path: root/machines/profpatsch
Commit message (Collapse)AuthorAgeFilesLines
* machines/katara: add jq, remove openvpn, fix gutenprintProfpatsch2017-11-221-11/+12
|
* machines/katara: switch back to network-managerProfpatsch2017-11-221-8/+8
| | | | | The wlp-supplicant module is just too buggy (especially after waking from standby it mostly doesn’t reinitialize the connection).
* machines/katara: config should not use recProfpatsch2017-11-221-1/+1
| | | | That’s from back when I wasn’t accustomed to the module system yet.
* machines/profpatsch: always clean /tmp on rebootProfpatsch2017-11-222-2/+3
|
* profpatsch/searx: Rebase searx-secret-key.patchaszlig2017-11-131-21/+21
| | | | | | | | | | This build error is quite annoying, so I applied the patch on v0.11.0 and rebased it against v0.12.0. The only hunk that's failing is the import of get_secret_app_key in searx/webapp.py, so no big conflicts with the actual logic of the patch. Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* machines/katara: Fix eval error for taalo-buildaszlig2017-11-131-1/+1
| | | | | | | | | | | The config attribute set is recursive, so "vuizvui" within that scope refers to the "vuizvui" attribute within config directly instead of using the one from pkgs. Prepending "pkgs." explicitly to the attribute path now avoids this. Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* taalo-build: Rewrite as wrapper and move to pkgsaszlig2017-11-121-3/+1
| | | | | | | | | | | | | | | | | | | | We no longer use the legacy SSH store protocol for taalo but the new ssh-ng protocol, which makes the implementation of taalo-build a LOT less clunky. It also didn't make sense to have this as a NixOS module when we after all just emit a static store path without any stuff depending on configuration options. The new implementation basically just wraps nix-build and nix-store -r along with the right NIX_REMOTE variable. With Nix 1.2 this can also be done with the new "nix build" command using the --store option, but unfortunately "nix build" doesn't yet have the same functionality as nix-build. Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch, @bendlas
* machines/katara: remove sentProfpatsch2017-11-083-22/+1
| | | | Patch doesn’t apply, I don’t use it anymore.
* machines/katara: Update microcodeProfpatsch2017-10-311-0/+2
| | | | My wifi module broke, because the microcode was too old and that option not set.
* machines/katara: rm TERM (it’s not what I thought it is)Profpatsch2017-09-201-1/+0
| | | | thx @aszlig
* machines/katara: add static vpn client to hakuProfpatsch2017-09-201-0/+11
|
* machines/haku: Revert setting addSSL to trueaszlig2017-09-011-1/+0
| | | | | | | | | | | | | This reverts commit 0cfbc3bcd4be9ba3798f1752f82f6ea2d3aba650. Since NixOS/nixpkgs@ae9d311565d8c790900ebbc0976e447034930112 the addSSL option is now mutually exclusive to forceSSL. Turns out that this actually was a bug that got introduced in NixOS/nixpkgs@a912a6a291eaa5f6a2ad9143c9e276779c357a41. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* haku: add static vpn interfaceProfpatsch2017-09-011-0/+8
|
* machines/haku: add test mailinglistProfpatsch2017-09-011-1/+1
|
* machines/haku: Fix evaluation error for nginxaszlig2017-08-191-0/+1
| | | | | | | | In order to use forceSSL you now also need to use addSSL and there is an assertion now to check that since NixOS/nixpkgs@a912a6a291eaa5f6a2ad914. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* profpatsch/pkgs: Fix attribute for searxaszlig2017-08-011-1/+1
| | | | | | | | | | Since NixOS/nixpkgs@c217f48c358db05bd0ad7893e8e3ebabe4784cbe, the searx package is no longer in pythonPackages but a top-level attribute. Tested eval by "nix-instantiate machines -A profpatsch.haku.build". Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* machines/profpatsch: enable fcitx & mozc japanese IMEProfpatsch2017-07-171-0/+4
|
* machines/haku: forgot the firewall exception for searxProfpatsch2017-07-101-1/+3
|
* machines/haku: move searx from katara to hakuProfpatsch2017-07-102-5/+5
|
* machines/katara: back to wpa_supplicant againProfpatsch2017-07-101-8/+8
|
* machines/katara: add TERM to the environmentProfpatsch2017-07-101-0/+2
|
* machines/katara: add anki plugin depsProfpatsch2017-07-101-1/+1
|
* modules/profpatsch/scannning: add option to list remote scannersProfpatsch2017-07-101-1/+6
| | | | | sane has a file called `net.conf` which is a list of hosts that are searched for remote scanners.
* machines/haku: remove pub subdomain againProfpatsch2017-07-081-8/+3
| | | | | Apparently `enableACME` doesn’t generate certificates for the right subdomains if they are on the same machine in different virtual hosts.
* machines/haku: add a pub subdomainProfpatsch2017-07-081-3/+8
|
* machines/haku: fix warpspeed serviceProfpatsch2017-07-081-2/+2
|
* machines/haku: add correct port numberProfpatsch2017-07-081-0/+2
|
* machines/katara: fix evaluation errorProfpatsch2017-07-081-1/+0
|
* machines/haku: refactor a bit to include into base server configProfpatsch2017-07-083-7/+43
| | | | | Until now, the config on the actual server was deviating because I changed it locally.
* profpatsch/jmtpfs: Drop vuizvui packageaszlig2017-06-221-1/+1
| | | | | | | | | | | | | | | | | The package fails because the mtp-jolla.patch was already applied upstream, see the following build log: https://headcounter.org/hydra/log/d21f1590i2hs6xhgkdr00906ksnvgxfz-libmtp-1.1.13.drv This is the upstream commit by @Profpatsch that's now part of libmtp version 1.1.13: https://sourceforge.net/p/libmtp/code/ci/8919ebeef58251639454c2394c0274597be3df9c/ Tested by evaluating machines.profpatsch.katara. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* machines/katara: change mouse speedsProfpatsch2017-05-312-18/+19
|
* pkgs/profpatsch/backlight: initProfpatsch2017-05-311-0/+1
|
* machines/katara: Fix attribute for hledgeraszlig2017-05-021-1/+1
| | | | | | | | | | | | | | Evaluation error introduced by 736e0da1e251df836b1669ffee80cecfd6bbf0e9. The attribute "hledger" isn't a top-level pkgs attribute but resides within haskellPackages. This fixes evaluation, as tested by: nix-instantiate machines -A profpatsch.katara.build Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* machines/katara: add hledgerProfpatsch2017-05-021-0/+1
|
* machines/katara: maybe not nix-gen yetProfpatsch2017-04-272-11/+11
|
* machines/katara: add nix-gen and modified searxProfpatsch2017-04-262-14/+19
|
* machines/katara: misc packagesProfpatsch2017-04-261-3/+6
|
* machines/katara: fontconfig presetProfpatsch2017-04-261-0/+1
|
* machines/katara: switch to network-manager againProfpatsch2017-04-261-18/+20
| | | | Hopefully temporarily.
* machines/profpatsch: move mutableUsers to baseProfpatsch2017-04-262-2/+3
|
* pkgs/show-qr-code: Move into pkgs/profpatschaszlig2017-04-231-3/+3
| | | | | | | | | Tested evaluation using: nix-instantiate pkgs -A vuizvui.profpatsch.show-qr-code Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* pkgs: Move jmtpfs to pkgs/profpatschaszlig2017-04-231-1/+1
| | | | | | | | This clearly is something currently only @Profpatsch wants, so lets move it into the user namespace. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* pkgs/profpatsch: add nmanProfpatsch2017-04-061-0/+1
|
* machines/katara: fix changes with fontconfig.ultimateProfpatsch2017-04-041-2/+4
|
* machines/katara: correct searx overrideProfpatsch2017-03-031-7/+15
|
* machines/katara: opengl 32bit support for steamProfpatsch2017-03-031-0/+4
|
* pkgs/profpatsch: remove requirements part from searx patchProfpatsch2017-02-231-20/+0
| | | | Patching the requirements.txt caused searx build to fail in the newer version.
* machines/katara: bonding is my fetishProfpatsch2017-02-231-0/+11
| | | | New-style bond wifi & ethernet, default to the faster ethernet if plugged in.
* machines/katara: add pretty-show to default ghcProfpatsch2017-02-231-1/+1
|
* machines/katara: searx anti-soundcloud patchProfpatsch2017-02-123-1/+19
| | | | | Soundcloud sometimes fails startup of searx, since it’s not actively used here it’s patched out until upstream resolves the issue.