a2bf9a7e60
hosts/ni/setups/desktop: configure i18n setup per-workflow
2024-01-04 12:04:31 +08:00
701a1b609f
profiles/dev: add hardware submodule
2023-12-25 20:05:49 +08:00
81443a5a9c
hosts/ni/networking/setup: enable resolved
2023-12-23 20:42:07 +08:00
9e170dd6ec
profiles/gaming: simplify the default setup
2023-12-22 08:57:41 +08:00
a6b5fca44c
secrets: update keys
2023-12-20 19:10:53 +08:00
fadf04b1d7
hosts/ni/networking/setup: update deprecated attributes
2023-12-20 10:52:00 +08:00
457638a65b
config: put all custom library functions under private namespace
2023-12-19 19:23:39 +08:00
35f2d5b9b8
config: add comments
2023-12-18 18:44:27 +08:00
40d286ac3a
profiles/dev: separate containers and virtual machines setup
2023-12-18 00:11:11 +08:00
3d94c89bea
profiles/dev: simplify the configuration
...
Now with host-specific and user-specific modules, we can now start
remove parts of the modules with my configurations on them that are
otherwise intended for the entire cluster.
2023-12-18 00:00:55 +08:00
3d4b8fa578
hosts/ni/setups/desktop: automatically set networking setup
2023-12-16 19:58:17 +08:00
c2a5840cce
tasks/multimedia-archive: migrate as ni's host-specific module
...
It is also used exclusively by that host so pretty much useless
as a shared module.
2023-12-15 20:22:08 +08:00
34047a49b4
tasks/backup-archive: migrate as ni's host-specific module
...
In practice, this is only used by it.
2023-12-15 14:14:15 +08:00
2f0d63ca95
hosts/ni: disable dhcpcd
...
It causes more trouble than benefits for its current setup.
2023-12-15 13:27:54 +08:00
b533507f40
chore: reformat codebase
2023-12-15 13:27:12 +08:00
cca53b9a46
hosts/ni/networking: add datetime settings
2023-12-13 10:54:26 +08:00
3f507705fb
hosts/ni/hardware/qol: add filesystem tools
2023-12-13 10:51:57 +08:00
9f673d64da
hosts/ni/setups/development: init module
2023-12-13 10:50:33 +08:00
2ce85e67c6
hosts/ni/setups/gaming: init module
2023-12-13 10:46:46 +08:00
bbb198d95b
hosts/ni/setups/desktop: init module
2023-12-13 10:45:29 +08:00
c6cd57d5bc
hosts/ni/setups/music: init module
2023-12-13 10:42:43 +08:00
8e42fa92d0
hosts/ni/networking: add enable option
2023-12-13 10:04:18 +08:00
3da9dc89fa
hosts/ni: modularize parts of the hardware setup
2023-12-12 21:28:41 +08:00
509ac5cdef
hosts/ni: format into new host-specific module structure
2023-12-12 21:20:55 +08:00
45a7e05cf7
hosts/ni: update Wireguard setup
2023-11-06 16:53:22 +08:00
3f291fe665
hosts/ni: modularize networking config
2023-11-06 16:10:42 +08:00
c410ece05a
treewide: remove options attribute for modules
2023-10-02 14:26:11 +08:00
c3bec31b86
chore: reformat codebase
2023-07-05 16:42:15 +08:00
2e7cdeacf3
hosts: remove host path prefix for sops keys
...
It is more explicit and elegant but more of a pain to manage especially
with the new function. It was structured that way for other hosts'
secrets but it isn't really used in practice. We could just enforce a
convention such as a `hosts` prefix to contain those secrets.
2023-07-05 13:11:47 +08:00
5fbd39adfc
hosts/ni: modularize Wireguard
...
I also added a conditional configuration for systemd-networkd and a
condition for the default which should be enabled when NetworkManager is
enabled. Ideally this should be the default when systemd-networkd is not
enabled but since they are the only network manager, we'll let it slide.
2023-07-05 11:40:40 +08:00
d4395da314
hosts/ni: move wireless configuration to appropriate file
2023-03-10 08:28:33 +08:00
8369ea4145
hosts/ni: switch to iwd for wireless network configuration
2023-03-09 11:43:47 +08:00
84b4e3be3e
hosts/ni: update systemd networking setup
2023-02-22 11:27:18 +08:00
8a23bd7932
hosts/ni: modularize networking configuration
...
Re-added the setup with the traditional networking configuration since
I'm currently using GNOME which only integrates with NetworkManager
which is working alongside it.
systemd-networkd not being used at this point but I'm keeping it.
2023-01-31 16:48:10 +08:00
