77c200a099
feat(inventree): add inventree subdomain to /etc/hosts
2024-08-20 14:12:55 +02:00
15eb4ea12f
feat(snipe-it): install snipe-it
2024-08-19 16:25:43 +02:00
9c0bf2a2df
feat(oil): delete files to trash
2024-08-18 14:13:08 +02:00
f206f131a2
fix(virt): do not store qcow2 images in git
2024-08-18 14:09:40 +02:00
65c726ecd2
feat(virt): enable hardware acceleration for qemu
2024-08-18 14:09:40 +02:00
bfcfe52d47
fix(borgbackup): also start backup service if system was powered down during scheduled time
2024-08-16 18:50:47 +02:00
b40cb35ab8
feat(keyboard): remap caps lock to ctrl
2024-08-16 18:48:03 +02:00
90aae41a83
fix: rename keyboard options to new names
2024-08-16 18:24:55 +02:00
409b192997
feat(nixvim): use telescope in more places using dressing.nvim
2024-08-16 16:45:26 +02:00
235d48135c
feat(nixvim): use frecency algorithm in telescope searches
...
This gives better results, especially in <leader>b
My first try was to use the frecency telescope plugin, but that seems to
add a new telescope command, while I want frecency sorting in all
commands.
I then found the telescope-all-recent[1] plugin, which seems to do what
I want. This seems best paired with dressing.nvim[2] or
telescope-ui-select[3], to use the telescope ui in all select operations
(kind of like ivy in emacs).
These plugins are not supported by nixvim natively, so I'm following the
guide on how to use these plugins[4].
This now works, but I'm kind of unhappy with the sorting. Emacs-ivy had
this really neat feature where the first ~5 elements of the result were
always the last 5 elements you picked. Maybe I can acheive that by
tweaking the frecency weights? Let's see in another commit.
[1] https://github.com/prochri/telescope-all-recent.nvim
[2] https://github.com/stevearc/dressing.nvim
[3] https://github.com/nvim-telescope/telescope-ui-select.nvim
[4] https://nix-community.github.io/nixvim/user-guide/faq.html
2024-08-16 16:29:22 +02:00
cd53c9bab8
feat(nixvim): install telescope-all-recent plugin
...
Configuration will be done in the next commit.
[1] https://github.com/prochri/telescope-all-recent.nvim
2024-08-16 15:37:14 +02:00
ea2cdf687f
chore: remove nonexistent input of flake-parts
2024-08-16 14:33:44 +02:00
67cd768b56
feat(zsh): install jujutsu completions
2024-08-15 17:07:49 +02:00
961d6a7293
feat(vcs): install jujutsu to user profile
2024-08-15 16:59:49 +02:00
37ad42b161
feat(nix-direnv): install nix-direnv
2024-08-14 13:48:04 +02:00
f9914e097d
feat(build tools): update build tools
2024-08-14 12:12:17 +02:00
c6f98edd88
chore: remove unused home-manager config
2024-08-14 12:11:37 +02:00
1c9ffc8fa0
fix(wm): include wm config
2024-08-14 12:10:46 +02:00
f4cb1f9690
fix(wm): move wm config
2024-08-14 12:03:26 +02:00
163ab6b3c0
fix(stylix): move wallpapers
2024-08-13 18:50:44 +02:00
14a4564a45
fix(home-manager): add colorscheme file
2024-08-13 18:50:21 +02:00
8ed040dd0e
fix(stylix): difference between nixos & home-manager options
2024-08-13 18:49:26 +02:00
48ad6caec9
wip(stylix): move stylix to nixos config
2024-08-13 17:20:02 +02:00
df92bdfe64
chore: remove files which were moved to nixos/
2024-08-13 16:57:48 +02:00
cc35787cab
fix(river-shifttags): forgot to change package install syntax
2024-08-13 13:40:44 +02:00
a499db635c
fix(river-shifttags): add missing river-shifttags input to nixos flake
2024-08-13 13:39:47 +02:00
f8931dc714
chore: update name of nixvim flake to be more consistent
2024-08-13 13:36:35 +02:00
f81036e0c6
chore(home-manager): remove unused input
2024-08-13 13:36:03 +02:00
390e3c6be4
fix(home-manager): argument was not in the correct place
2024-08-13 13:34:08 +02:00
10301e5d35
fix(nixvim): try to specify the package directly in flake.nix
2024-08-13 13:32:08 +02:00
098f6e9f62
update nixvim/flake.lock
2024-08-13 13:24:23 +02:00
ec8047a5ca
fix(nixvim): follow nixpkgs
2024-08-13 12:55:20 +02:00
e46d874e51
fix(home-manager): copy over nixvim configuration
2024-08-13 12:44:43 +02:00
64bc5aae14
feat(home-manager): slowly migrate home-manager to be installed as a nixos module
2024-08-13 12:41:45 +02:00
0dd923adaf
fix(home-manager): import only the homeConfiguration, not the whole flake
2024-08-13 09:29:44 +02:00
5eec06c38d
feat(home-manager): try managing home-manager configuration through configuration.nix
...
This will allow nixos-rebuild build-vm to already have a configured
system, simplifing testing.
2024-08-13 09:22:54 +02:00
6dd0a1f9c8
fix(fprintd): make nixos-06cb-009a-fingerprint-sensor follow nixpkgs
...
This may speed up evaluation times
2024-08-13 09:22:26 +02:00
87a8507834
feat(apply): update apply.sh
...
NIXOS_LABEL does not seem to work, so I'm removing it.
I'm also launching gitu, to encourage frequent commits.
2024-08-13 09:16:35 +02:00
2ba86baac8
feat(logs): install lnav
2024-08-13 09:01:04 +02:00
c0a1443ba9
feat(vm): configure initial password for users to allow login
2024-08-13 08:47:02 +02:00
e64cf18222
feat(backup): first borgbackup module test
...
https://xeiaso.net/blog/borg-backup-2021-01-09/
2024-08-12 16:58:39 +02:00
1c362fbf82
feat(openssh): enable openssh server
2024-08-12 14:42:14 +02:00
82fa9c473b
feat(apply.sh): launch gitu before rebuilding config, to encourage committing
2024-08-12 14:18:40 +02:00
dabd4298a6
fix(sourcehut): actually environment.variables do not affect systemd services, trying another way
2024-08-12 14:17:05 +02:00
b895943359
fix(sourcehut): make python's requests use global ca-certificates store
2024-08-12 13:50:42 +02:00
406d1cc6ca
chore(sourcehut): remove all traces of custom cacert package fuckery
...
I found out that you can set an env variable to make python's request
use the global cert store, this sidesteps the issue I have been having
with sourcehut.
2024-08-12 13:49:37 +02:00
57dacc328b
fix(sourcehut): try using patched cacert using a module?
...
Let's see if this works
2024-08-12 13:07:43 +02:00
38b50dd127
Revert "fix(remote build): set PATH environment variable required for nix acces on remote shell"
...
This reverts commit c37724ec6d .
Actually the config needs to be systemwide
2024-08-11 17:41:48 +02:00
9ed7765667
chore: remove ssh configuration
...
Actually, I misread the tutorial, this configuration should be done on
the remote machine.
2024-08-11 17:35:33 +02:00
332a0cc4c8
fix(ssh config): actually use the correct options
2024-08-11 17:18:50 +02:00