| 25 Mar 2024 |
 conr | like commit it to my repo? | 01:45:25 |
| conr | * so for lanzaboote, do i need the niv nix folder forever? | 01:45:43 |
| conr | maybe i need to integrate it with my flake? | 01:50:22 |
| conr | i'll ask secure-boot | 01:50:55 |
|  ttamttam joined the room. | 01:58:40 |
| conr left the room. | 03:24:13 |
|  nazarewk joined the room. | 19:46:09 |
|  ma27 joined the room. | 19:53:42 |
|  Alex Ou joined the room. | 20:08:57 |
|  konrad-thorson joined the room. | 20:12:53 |
| konrad-thorson | Howdy | 20:13:13 |
| konrad-thorson | I'm playing with an idea and would appreciate some feedback from people that understand Nix OS better than I do. Basically I want to make a NixOS.img operating system installer that includes IPFS. Once the ipfs node starts following a pin set of nix packages then install from ipfs, but also run the binaries from the ipfs file store. For me this is an 'art project' involving computing and the idea of https://en.wikipedia.org/wiki/Ship_of_Theseus Nix seems perfect for configuration of the software side of things. | 20:14:46 |
| 26 Mar 2024 |
|  Maximilian Gaedig ⚡️ joined the room. | 15:09:51 |
| 27 Mar 2024 |
| Room Avatar Renderer. | 13:39:52 |
| 26 Mar 2024 |
| Alex Ou | konrad-thorson: I'm not familiar with ipfs, but as far as a custom installer with your own packages and configs, here's an example of an installer that has an option to configure tailscale, would be easy to set up some more systemd services to start binaries. Not sure if you meant you wanted the installer to install and then run stuff, or for the installer instance to run stuff (the example shows more the latter, but you could configure the installed flake to do the former) https://github.com/femtodata/nixos-flake-installer | 16:07:55 |
| 29 Mar 2024 |
|  SebTM joined the room. | 04:23:10 |
|  pareto-optimal-dev joined the room. | 17:22:02 |
| pareto-optimal-dev left the room. | 17:24:14 |
| 30 Mar 2024 |
|  AJCxZ0 joined the room. | 00:40:15 |
| 31 Mar 2024 |
|  blu3 joined the room. | 17:38:16 |
| blu3 | hi | 17:44:18 |
| blu3 | Redacted or Malformed Event | 17:58:36 |
| blu3 | Redacted or Malformed Event | 17:58:39 |
| blu3 | Redacted or Malformed Event | 17:59:47 |
|  skip joined the room. | 20:34:57 |
| blu3 changed their display name from dclmatrix to exet. | 22:32:51 |
|  Miles Dyson joined the room. | 23:04:12 |
| Miles Dyson | Hey there, I am a NixOS noob.
NisOS has been installed for a few weeks and we are getting to know each other.
What are different methods for organizing the config files?
I have opted to create the sub directory '/etc/nixos/import'.
Within './import' there are additional directories to organize the config files.
Is this a common practice, are there any standards?
There I created additional sub directories for different configuration types. | 23:14:03 |
 raitobezarius | there's no standards, but plenty of repositories online you can easily find on github which can give you opinions on that | 23:14:39 |
| Miles Dyson | The directory structure I have set up looks like this:
`[/etc]$ tree -L 3 -d ./nixos
./nixos
└── import
├── base
├── development
│ ├── editor
│ ├── revision
│ ├── shell
│ └── terminal
├── display
├── engineering
├── game
├── management
├── media
│ ├── audio
│ ├── graphics
│ ├── image
│ ├── players-library-downloaders
│ └── video
├── network
│ ├── communications
│ ├── connections
│ ├── locale
│ ├── server
│ ├── tools
│ └── wireless
├── office
├── projects
│ └── intelligence
└── utilites-system
29 directories`
Does it seem reasonable? | 23:15:38 |
