NixOS modules move one level up because it's unlikely that //ops/nixos will contain actual systems at this point (they're user-specific). This is the first users folder, so it is also added to the root readTree invocation for the repository. Change-Id: I546c701145fa204b7ba7518a8a56a783588629e0 Reviewed-on: https://cl.tvl.fyi/c/depot/+/244 Reviewed-by: tazjin <mail@tazj.in>
		
			
				
	
	
		
			20 lines
		
	
	
	
		
			683 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			20 lines
		
	
	
	
		
			683 B
		
	
	
	
		
			Markdown
		
	
	
	
	
	
| NixOS configuration
 | |
| ===================
 | |
| 
 | |
| My NixOS configuration! It configures most of the packages I require
 | |
| on my systems, sets up Emacs the way I need and does a bunch of other
 | |
| interesting things.
 | |
| 
 | |
| System configuration lives in folders for each machine and a custom
 | |
| fixed point evaluation (similar to standard NixOS module
 | |
| configuration) is used to combine configuration together.
 | |
| 
 | |
| Building `ops.nixos.rebuilder` yields a script that will automatically
 | |
| build and activate the newest configuration based on the current
 | |
| hostname.
 | |
| 
 | |
| ## Configured hosts:
 | |
| 
 | |
| * `frog` - weapon of mass computation at home
 | |
| * `nugget` - desktop computer at home
 | |
| * ~~`urdhva` - T470s~~ (currently with edef)
 |