Gleipnir/nixos-systems
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
nixos-systems/flake.lock

710 lines
19 KiB
Text
Raw Normal View History

Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
{
"nodes": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"authentik-nix": {
"inputs": {
"authentik-src": "authentik-src",
"flake-compat": "flake-compat",
"flake-parts": "flake-parts",
"flake-utils": "flake-utils",
"napalm": "napalm",
"nixpkgs": "nixpkgs",
"pyproject-build-systems": "pyproject-build-systems",
"pyproject-nix": "pyproject-nix",
"systems": "systems",
"uv2nix": "uv2nix"
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1763643080,
"narHash": "sha256-jlYmjrTw3g5iOYDZBGb5Plw6IyRa+WY60e3GzU19bkk=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "nix-community",
"repo": "authentik-nix",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "4a670757083d94a9dceb4929eb88eb9995bc1363",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "nix-community",
"repo": "authentik-nix",
"type": "github"
}
},
"authentik-src": {
"flake": false,
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1763564826,
"narHash": "sha256-xBnAfoAOUslOrxNzY5kV0h67qWMXKZnPC/wgRGXZleQ=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "goauthentik",
"repo": "authentik",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "2fedc3d0a0ba91c16bb71bd4b2432108ca02e890",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "goauthentik",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"ref": "version/2025.10.2",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"repo": "authentik",
"type": "github"
}
},
Attempt to make new corp hardware the definitive corp hardware This is...a big change. If I run this on the old corp server it will break a lot, LOT of stuff. So don't do that. This is also the first time I'm attempting to use disko to fully define a server in a single step rather than as a bootstrapping step.
2025-09-08 20:36:59 +00:00
"disko": {
"inputs": {
"nixpkgs": [
"nixpkgs"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765794845,
"narHash": "sha256-YD5QWlGnusNbZCqR3pxG8tRxx9yUXayLZfAJRWspq2s=",
Attempt to make new corp hardware the definitive corp hardware This is...a big change. If I run this on the old corp server it will break a lot, LOT of stuff. So don't do that. This is also the first time I'm attempting to use disko to fully define a server in a single step rather than as a bootstrapping step.
2025-09-08 20:36:59 +00:00
"owner": "nix-community",
"repo": "disko",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "7194cfe5b7a3660726b0fe7296070eaef601cae9",
Attempt to make new corp hardware the definitive corp hardware This is...a big change. If I run this on the old corp server it will break a lot, LOT of stuff. So don't do that. This is also the first time I'm attempting to use disko to fully define a server in a single step rather than as a bootstrapping step.
2025-09-08 20:36:59 +00:00
"type": "github"
},
"original": {
"owner": "nix-community",
"repo": "disko",
"type": "github"
}
},
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"fieldseeker-sync": {
"inputs": {
"flake-utils": "flake-utils_2",
"nixpkgs": "nixpkgs_2"
},
"locked": {
Bump version of fieldseeker-sync
2025-10-31 16:22:24 +00:00
"lastModified": 1761839629,
"narHash": "sha256-vUw8AEIVdZ3F+ZW4Mjcwr1/2qY5aci5dICaV81WLLzY=",
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"owner": "Gleipnir-Technology",
"repo": "fieldseeker-sync",
Bump version of fieldseeker-sync
2025-10-31 16:22:24 +00:00
"rev": "e250e0abbb35f6d64851305d3b59c4ed1d968bc8",
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"type": "github"
},
"original": {
"owner": "Gleipnir-Technology",
"repo": "fieldseeker-sync",
Bump version of fieldseeker-sync
2025-10-31 16:22:24 +00:00
"rev": "e250e0abbb35f6d64851305d3b59c4ed1d968bc8",
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"type": "github"
}
},
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"flake-compat": {
"flake": false,
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1761588595,
"narHash": "sha256-XKUZz9zewJNUj46b4AJdiRZJAvSZ0Dqj2BNfXvFlJC4=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "edolstra",
"repo": "flake-compat",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "f387cd2afec9419c8ee37694406ca490c3f34ee5",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "edolstra",
"repo": "flake-compat",
"type": "github"
}
},
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"flake-parts": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"inputs": {
"nixpkgs-lib": "nixpkgs-lib"
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1762980239,
"narHash": "sha256-8oNVE8TrD19ulHinjaqONf9QWCKK+w4url56cdStMpM=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "hercules-ci",
"repo": "flake-parts",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "52a2caecc898d0b46b2b905f058ccc5081f842da",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "hercules-ci",
"repo": "flake-parts",
"type": "github"
}
},
"flake-parts_2": {
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"inputs": {
"nixpkgs-lib": [
"nixvim",
"nixpkgs"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765495779,
"narHash": "sha256-MhA7wmo/7uogLxiewwRRmIax70g6q1U/YemqTGoFHlM=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "hercules-ci",
"repo": "flake-parts",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "5635c32d666a59ec9a55cab87e898889869f7b71",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "hercules-ci",
"repo": "flake-parts",
"type": "github"
}
},
"flake-utils": {
"inputs": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"systems": [
"authentik-nix",
"systems"
]
},
"locked": {
"lastModified": 1731533236,
"narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
"owner": "numtide",
"repo": "flake-utils",
"rev": "11707dc2f618dd54ca8739b309ec4fc024de578b",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
"flake-utils_2": {
"inputs": {
"systems": "systems_2"
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
},
"locked": {
"lastModified": 1731533236,
"narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
"owner": "numtide",
"repo": "flake-utils",
"rev": "11707dc2f618dd54ca8739b309ec4fc024de578b",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"flake-utils_3": {
"inputs": {
"systems": "systems_3"
},
"locked": {
"lastModified": 1731533236,
"narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
"owner": "numtide",
"repo": "flake-utils",
"rev": "11707dc2f618dd54ca8739b309ec4fc024de578b",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"flake-utils_4": {
"inputs": {
"systems": "systems_4"
},
"locked": {
"lastModified": 1731533236,
"narHash": "sha256-l0KFg5HjrsfsO/JpG+r7fRrqm12kzFHyUHqHCVpMMbI=",
"owner": "numtide",
"repo": "flake-utils",
"rev": "11707dc2f618dd54ca8739b309ec4fc024de578b",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"home-manager": {
"inputs": {
"nixpkgs": [
"nixpkgs"
]
},
"locked": {
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"lastModified": 1763992789,
"narHash": "sha256-WHkdBlw6oyxXIra/vQPYLtqY+3G8dUVZM8bEXk0t8x4=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "nix-community",
"repo": "home-manager",
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"rev": "44831a7eaba4360fb81f2acc5ea6de5fde90aaa3",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "nix-community",
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"ref": "release-25.05",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"repo": "home-manager",
"type": "github"
}
},
"ixx": {
"inputs": {
"flake-utils": [
"nixvim",
"nuschtosSearch",
"flake-utils"
],
"nixpkgs": [
"nixvim",
"nuschtosSearch",
"nixpkgs"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1754860581,
"narHash": "sha256-EM0IE63OHxXCOpDHXaTyHIOk2cNvMCGPqLt/IdtVxgk=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "NuschtOS",
"repo": "ixx",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "babfe85a876162c4acc9ab6fb4483df88fa1f281",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "NuschtOS",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"ref": "v0.1.1",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"repo": "ixx",
"type": "github"
}
},
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"napalm": {
"inputs": {
"flake-utils": [
"authentik-nix",
"flake-utils"
],
"nixpkgs": [
"authentik-nix",
"nixpkgs"
]
},
"locked": {
"lastModified": 1725806412,
"narHash": "sha256-lGZjkjds0p924QEhm/r0BhAxbHBJE1xMOldB/HmQH04=",
"owner": "willibutz",
"repo": "napalm",
"rev": "b492440d9e64ae20736d3bec5c7715ffcbde83f5",
"type": "github"
},
"original": {
"owner": "willibutz",
"ref": "avoid-foldl-stack-overflow",
"repo": "napalm",
"type": "github"
}
},
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nidus-sync": {
"inputs": {
"flake-utils": "flake-utils_3",
"nixpkgs": "nixpkgs_3"
},
"locked": {
Update to nidus-sync 0.0.5
2025-12-15 16:00:47 +00:00
"lastModified": 1765814387,
"narHash": "sha256-2ki7oxXNHMeRuYEkOTTeS9aFKhejS63nzpT2EW6I04Y=",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"owner": "Gleipnir-Technology",
"repo": "nidus-sync",
Update to nidus-sync 0.0.5
2025-12-15 16:00:47 +00:00
"rev": "b31ca6c83ed96dbb1d15c94bcf57cfdb07a11b5a",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"type": "github"
},
"original": {
"owner": "Gleipnir-Technology",
"repo": "nidus-sync",
Update to nidus-sync 0.0.5
2025-12-15 16:00:47 +00:00
"rev": "b31ca6c83ed96dbb1d15c94bcf57cfdb07a11b5a",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"type": "github"
}
},
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"nixos-facter-modules": {
"locked": {
"lastModified": 1766558141,
"narHash": "sha256-Ud9v49ZPsoDBFuyJSQ2Mpw1ZgAH/aMwUwwzrVoetNus=",
"owner": "numtide",
"repo": "nixos-facter-modules",
"rev": "e796d536e3d83de74267069e179dc620a608ed7d",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "nixos-facter-modules",
"type": "github"
}
},
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"nixpkgs": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1763421233,
"narHash": "sha256-Stk9ZYRkGrnnpyJ4eqt9eQtdFWRRIvMxpNRf4sIegnw=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "NixOS",
"repo": "nixpkgs",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "89c2b2330e733d6cdb5eae7b899326930c2c0648",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-unstable",
"repo": "nixpkgs",
"type": "github"
}
},
"nixpkgs-lib": {
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1761765539,
"narHash": "sha256-b0yj6kfvO8ApcSE+QmA6mUfu8IYG6/uU28OFn4PaC8M=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "nix-community",
"repo": "nixpkgs.lib",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "719359f4562934ae99f5443f20aa06c2ffff91fc",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "nix-community",
"repo": "nixpkgs.lib",
"type": "github"
}
},
"nixpkgs_2": {
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"locked": {
"lastModified": 1759735786,
"narHash": "sha256-a0+h02lyP2KwSNrZz4wLJTu9ikujNsTWIC874Bv7IJ0=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "20c4598c84a671783f741e02bf05cbfaf4907cff",
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-25.05",
"repo": "nixpkgs",
"type": "github"
}
},
"nixpkgs_3": {
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"locked": {
"lastModified": 1761999846,
"narHash": "sha256-IYlYnp4O4dzEpL77BD/lj5NnJy2J8qbHkNSFiPBCbqo=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "3de8f8d73e35724bf9abef41f1bdbedda1e14a31",
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-25.05",
"repo": "nixpkgs",
"type": "github"
}
},
"nixpkgs_4": {
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765687488,
"narHash": "sha256-7YAJ6xgBAQ/Nr+7MI13Tui1ULflgAdKh63m1tfYV7+M=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "NixOS",
"repo": "nixpkgs",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "d02bcc33948ca19b0aaa0213fe987ceec1f4ebe1",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "NixOS",
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"ref": "nixos-25.05",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"repo": "nixpkgs",
"type": "github"
}
},
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nixpkgs_5": {
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765457389,
"narHash": "sha256-ddhDtNYvleZeYF7g7TRFSmuQuZh7HCgqstg5YBGwo5s=",
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"owner": "NixOS",
"repo": "nixpkgs",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "f997fa0f94fb1ce55bccb97f60d41412ae8fde4c",
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixpkgs-unstable",
"repo": "nixpkgs",
"type": "github"
}
},
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nixpkgs_6": {
Add timecard-bot deployment to corp This currently has the architecture hard-coded. That's bad, but nix is hard, and there's probably a much better way to integrate this into the system when I can be bothered to do it.
2025-09-26 19:08:26 +00:00
"locked": {
"lastModified": 1758763312,
"narHash": "sha256-puBMviZhYlqOdUUgEmMVJpXqC/ToEqSvkyZ30qQ09xM=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "e57b3b16ad8758fd681511a078f35c416a8cc939",
"type": "github"
},
"original": {
"id": "nixpkgs",
"type": "indirect"
}
},
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"nixvim": {
"inputs": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"flake-parts": "flake-parts_2",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"nixpkgs": [
"nixpkgs"
],
"nuschtosSearch": "nuschtosSearch",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"systems": "systems_5"
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765643213,
"narHash": "sha256-1JU2vcsRXwjrQoDpNc8+E13vLEu8MwLaVfBQ3ktWFUw=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "nix-community",
"repo": "nixvim",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "0e8b4ccf0a4e4e90f9ca39295e807628a6e575e6",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "nix-community",
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"ref": "nixos-25.05",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"repo": "nixvim",
"type": "github"
}
},
"nuschtosSearch": {
"inputs": {
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"flake-utils": "flake-utils_4",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"ixx": "ixx",
"nixpkgs": [
"nixvim",
"nixpkgs"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1761730856,
"narHash": "sha256-t1i5p/vSWwueZSC0Z2BImxx3BjoUDNKyC2mk24krcMY=",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"owner": "NuschtOS",
"repo": "search",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "e29de6db0cb3182e9aee75a3b1fd1919d995d85b",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"type": "github"
},
"original": {
"owner": "NuschtOS",
"repo": "search",
"type": "github"
}
},
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"pyproject-build-systems": {
"inputs": {
"nixpkgs": [
"authentik-nix",
"nixpkgs"
],
"pyproject-nix": [
"authentik-nix",
"pyproject-nix"
],
"uv2nix": [
"authentik-nix",
"uv2nix"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1761781027,
"narHash": "sha256-YDvxPAm2WnxrznRqWwHLjryBGG5Ey1ATEJXrON+TWt8=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "pyproject-nix",
"repo": "build-system-pkgs",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "795a980d25301e5133eca37adae37283ec3c8e66",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "pyproject-nix",
"repo": "build-system-pkgs",
"type": "github"
}
},
"pyproject-nix": {
"inputs": {
"nixpkgs": [
"authentik-nix",
"nixpkgs"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1763435975,
"narHash": "sha256-SKdpcVuJKMNEXloIpLXY+jDI42+6Ew21vdkl894DxHo=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "pyproject-nix",
"repo": "pyproject.nix",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "7d3d8848358ccbd415afe2139f12b9e1508d3ace",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "pyproject-nix",
"repo": "pyproject.nix",
"type": "github"
}
},
Add timecard-bot deployment to corp This currently has the architecture hard-coded. That's bad, but nix is hard, and there's probably a much better way to integrate this into the system when I can be bothered to do it.
2025-09-26 19:08:26 +00:00
"pyproject-nix_2": {
"inputs": {
"nixpkgs": [
"timecard-bot",
"nixpkgs"
]
},
"locked": {
"lastModified": 1758265079,
"narHash": "sha256-amLaLNwKSZPShQHzfgmc/9o76dU8xzN0743dWgvYlr8=",
"owner": "nix-community",
"repo": "pyproject.nix",
"rev": "02e9418fd4af638447dca4b17b1280da95527fc9",
"type": "github"
},
"original": {
"owner": "nix-community",
"repo": "pyproject.nix",
"type": "github"
}
},
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"root": {
"inputs": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"authentik-nix": "authentik-nix",
Attempt to make new corp hardware the definitive corp hardware This is...a big change. If I run this on the old corp server it will break a lot, LOT of stuff. So don't do that. This is also the first time I'm attempting to use disko to fully define a server in a single step rather than as a bootstrapping step.
2025-09-08 20:36:59 +00:00
"disko": "disko",
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"fieldseeker-sync": "fieldseeker-sync",
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"home-manager": "home-manager",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nidus-sync": "nidus-sync",
Add switch-fix commands
2026-01-05 00:27:23 +00:00
"nixos-facter-modules": "nixos-facter-modules",
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nixpkgs": "nixpkgs_4",
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"nixvim": "nixvim",
Add timecard-bot deployment to corp This currently has the architecture hard-coded. That's bad, but nix is hard, and there's probably a much better way to integrate this into the system when I can be bothered to do it.
2025-09-26 19:08:26 +00:00
"sops-nix": "sops-nix",
"timecard-bot": "timecard-bot"
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
}
},
"sops-nix": {
"inputs": {
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nixpkgs": "nixpkgs_5"
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1765836173,
"narHash": "sha256-hWRYfdH2ONI7HXbqZqW8Q1y9IRbnXWvtvt/ONZovSNY=",
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"owner": "Mic92",
"repo": "sops-nix",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "443a7f2e7e118c4fc63b7fae05ab3080dd0e5c63",
Add secrets and home config to the corp machine
2025-07-16 09:55:20 -07:00
"type": "github"
},
"original": {
"owner": "Mic92",
"repo": "sops-nix",
"type": "github"
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
}
},
"systems": {
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"locked": {
"lastModified": 1689347949,
"narHash": "sha256-12tWmuL2zgBgZkdoB6qXZsgJEH9LR3oUgpaQq2RbI80=",
"owner": "nix-systems",
"repo": "default-linux",
"rev": "31732fcf5e8fea42e59c2488ad31a0e651500f68",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default-linux",
"type": "github"
}
},
"systems_2": {
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"locked": {
"lastModified": 1681028828,
"narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
"owner": "nix-systems",
"repo": "default",
"rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default",
"type": "github"
}
},
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"systems_3": {
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
"locked": {
"lastModified": 1681028828,
"narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
"owner": "nix-systems",
"repo": "default",
"rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default",
"type": "github"
}
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
},
Make fieldseeker-sync a flake input Makes it easier to update since I just bump the commit ID and then it'll deploy
2025-10-07 18:24:58 +00:00
"systems_4": {
"locked": {
"lastModified": 1681028828,
"narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
"owner": "nix-systems",
"repo": "default",
"rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default",
"type": "github"
}
},
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"systems_5": {
"locked": {
"lastModified": 1681028828,
"narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
"owner": "nix-systems",
"repo": "default",
"rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default",
"type": "github"
}
},
Add timecard-bot deployment to corp This currently has the architecture hard-coded. That's bad, but nix is hard, and there's probably a much better way to integrate this into the system when I can be bothered to do it.
2025-09-26 19:08:26 +00:00
"timecard-bot": {
"inputs": {
Add nidus-sync production module This will allow me to keep nidus-sync stable while continuing to do development on this same server on a different port.
2025-11-11 17:24:07 +00:00
"nixpkgs": "nixpkgs_6",
Add timecard-bot deployment to corp This currently has the architecture hard-coded. That's bad, but nix is hard, and there's probably a much better way to integrate this into the system when I can be bothered to do it.
2025-09-26 19:08:26 +00:00
"pyproject-nix": "pyproject-nix_2"
},
"locked": {
"lastModified": 1758911329,
"narHash": "sha256-ZYAG5ZegC+NjH59Jgmi1lyn2UyyVHzvC3UVm99wIE4M=",
"owner": "Gleipnir-Technology",
"repo": "timecard-bot",
"rev": "8c81b6683f97aa2712323836e629adf102be58ac",
"type": "github"
},
"original": {
"owner": "Gleipnir-Technology",
"repo": "timecard-bot",
"rev": "8c81b6683f97aa2712323836e629adf102be58ac",
"type": "github"
}
},
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"uv2nix": {
"inputs": {
"nixpkgs": [
"authentik-nix",
"nixpkgs"
],
"pyproject-nix": [
"authentik-nix",
"pyproject-nix"
]
},
"locked": {
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"lastModified": 1763421857,
"narHash": "sha256-8JurcmEzAkrpm+eUDm8W/+KkU/w/viAeyJhJlIX2qOQ=",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"owner": "pyproject-nix",
"repo": "uv2nix",
Add restic backup for all corp services
2026-01-12 00:48:54 +00:00
"rev": "c9752c6c5915eece99505612d8f7805185cff990",
Get authentik working on the new corp server without podman The podman integration was pretty janky because it relied on running a pod and the NixOS integration with pods are essentially non-existent. This led to issues with the port being improperly forwarded when partially restarted. Now instead I use a flake dedicated to running authentik. This allows me to specify some of the config in the module directly and some in secrets, which is really nice. I've additionally added some changes to the listen address so that the service isn't exposed over public IP addresses.
2025-09-09 13:01:14 +00:00
"type": "github"
},
"original": {
"owner": "pyproject-nix",
"repo": "uv2nix",
"type": "github"
}
Migrate corp configuration to this repository and use flakes
2025-07-16 09:32:19 -07:00
}
},
"root": "root",
"version": 7
}
Reference in a new issue Copy permalink