| 9 Feb 2024 |
 pgibson | Is this the correct way to import a flake from a subdir? ```
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11";
dockerSshTunnel.url = "path:./docker-ssh-tunnel";
};
| 03:44:30 |
| pgibson | * Is this the correct way to import a flake from a subdir?
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11";
dockerSshTunnel.url = "path:./docker-ssh-tunnel";
};
| 03:44:43 |
| pgibson | Or should I be using imports = [...] | 03:51:11 |
 treed | If you want to update an input, it's nix flake lock --update-input $input-name | 23:24:22 |
| treed | That'll update to the latest version | 23:24:32 |
| treed | And I have no experience with local flakes, other than knowing that . is a reference to the local flake. So maybe just ./docker-ssh-tunnel | 23:25:18 |
| treed | Although if it's working with the path prefix, then that's probably also fine | 23:25:30 |
| treed | * And I have no experience with local flakes, other than knowing that . is a reference to the local directory's flake. So maybe just ./docker-ssh-tunnel | 23:28:22 |
| treed | * And I have no experience with local flakes, other than knowing that . is a reference to the current directory's flake. So maybe just ./docker-ssh-tunnel | 23:28:30 |
| pgibson | Appears to use the name that you import it under in your outer flake inputs | 23:28:35 |
| treed | yeah, the name should be as listed in the inputs so dockerSshTunnel in your case | 23:29:03 |
| pgibson | Steep learning curve, but being able to define a server with containers running as a service in a hundred LoC is pretty awesome | 23:31:23 |
| treed | Yeah, my homelab has like 25 VMs and it's all from just over 5k LoC | 23:35:43 |
| treed | I've done cfengine, puppet, chef, saltstack, ansible. This is by far the smoothest experience, once you figure out what you're doing | 23:36:04 |
| treed | I still have to use ansible for the hypervisors (proxmox) and I get agitated every time | 23:36:24 |
