## 📋 Pull Request Information **Original PR:** https://github.com/patrickchugh/terravision/pull/160 **Author:** [@tlehman](https://github.com/tlehman) **Created:** 1/22/2026 **Status:** ✅ Merged **Merged:** 1/22/2026 **Merged by:** [@patrickchugh](https://github.com/patrickchugh) **Base:** `main` ← **Head:** `nix-flake` --- ### 📝 Commits (1) - [`eec987a`](https://github.com/patrickchugh/terravision/commit/eec987abdd34d3a298318535e1c62762d30a320d) Add Nix flake as Option 3 ### 📊 Changes **3 files changed** (+179 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+15 -0) ➕ `flake.lock` (+61 -0) ➕ `flake.nix` (+103 -0) </details> ### 📄 Description # Add third installation option (not docker, not native, but nix) I don't like installing python stuff on my host machine, and I also think docker is overkill. Nix is a nice sweet spot between the two, since it has filesystem isolation like docker, but without all the process namespace overhead. ## Type of Change * [ ] Bug Fix * [x] New Feature * [ ] Refactor * [x] Documentation ## Checklist All Submissions: * [x] Have you checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change? * [x] Have you written Documentation/Tests? * [x] Have you done your own code-review? * [ ] Have you disclosed any use of AI tools and models with their version? ## AI Assistance Declaration - Tools used: Claude Code - Model: Claude Opus 4.5 - Scope: Generated Nix flake ### Checklist for Changes to Core Features: * [ ] Have you discussed any major revamp with a reviewer/maintainer first? (It's okay to just raise a PR directly for minor bugfixes) * [x] Have you ensured your PR is focused on one major improvement and is not trying to do too many changes at once? For example: Bad : Adding support for GCP and Azure system wide Good: Just adding Azure resource handler for VNets * [x] Have you added an explanation of what your changes do and why you'd like us to include them? * [ ] Have you written new tests for your core changes, as applicable, and made sure the new tests PASS? (no, but I tested it using Determinate Nix 3.11.2 and it works) * [x] Have you successfully run all previous system wide tests with your changes locally? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

BreizhHardware commented

2026-05-06 12:38:04 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/patrickchugh/terravision/pull/160
Author: @tlehman
Created: 1/22/2026
Status: ✅ Merged
Merged: 1/22/2026
Merged by: @patrickchugh

Base: main ← Head: nix-flake

📝 Commits (1)

eec987a Add Nix flake as Option 3

📊 Changes

3 files changed (+179 additions, -0 deletions)

View changed files

📝 README.md (+15 -0)
➕ flake.lock (+61 -0)
➕ flake.nix (+103 -0)

📄 Description

Add third installation option (not docker, not native, but nix)

I don't like installing python stuff on my host machine, and I also think docker is overkill. Nix is a nice sweet spot between the two, since it has filesystem isolation like docker, but without all the process namespace overhead.

Type of Change

Bug Fix
New Feature
Refactor
Documentation

Checklist

All Submissions:

Have you checked to ensure there aren't other open Pull Requests for the same update/change?
Have you written Documentation/Tests?
Have you done your own code-review?
Have you disclosed any use of AI tools and models with their version?

AI Assistance Declaration

Tools used: Claude Code
Model: Claude Opus 4.5
Scope: Generated Nix flake

Checklist for Changes to Core Features:

Have you discussed any major revamp with a reviewer/maintainer first? (It's okay to just raise a PR directly for minor bugfixes)
Have you ensured your PR is focused on one major improvement and is not trying to do too many changes at once? For example:
Bad : Adding support for GCP and Azure system wide
Good: Just adding Azure resource handler for VNets
Have you added an explanation of what your changes do and why you'd like us to include them?
Have you written new tests for your core changes, as applicable, and made sure the new tests PASS? (no, but I tested it using Determinate Nix 3.11.2 and it works)
Have you successfully run all previous system wide tests with your changes locally?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

BreizhHardware

closed this issue
added the
pull-request
label

Rows
Columns

[PR #160] [MERGED] Add Nix flake as Option 3 #185