Add nix flake

[6543]

to make it easy to create development environments that are reproducible

What type of PR is this?

• documentation ?

What this PR does / why we need it:

this project has a lot of dependencies to be compiled correctly ... and if you want to run it outside of docker it's hard to build it for that.

Which issue(s) this PR fixes:

none instead of creating an issue first i created this pull so actuall discustion can happen alongide the code

Special notes for your reviewer:

well if you don't use nix the files do not interfere with the rest at all

Testing

install nix and do:

nix develop

Summary by CodeRabbit

• Chores
  • Added Nix flake configuration to provide a consistent development environment across systems with Go 1.24, Node.js 22, TypeScript, and comprehensive build tooling for both frontend and backend development.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new Nix flake configuration file is added at the project root, defining development environment inputs and per-system outputs. The devShell includes Go 1.24, Node.js 22, pnpm, TypeScript, golangci-lint, and various build tools with environment variables configured for compilation.

Changes

Cohort / File(s)	Summary
Nix Flake Configuration flake.nix	New file: Nix flake defining inputs (nixpkgs, flake-utils), per-system devShell outputs with Go 1.24, Node.js 22, pnpm, TypeScript, golangci-lint, sqlite, and image/format libraries. Sets CFLAGS, LDFLAGS, GO, and GOROOT environment variables.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Security Note: Review CFLAGS and LDFLAGS values to ensure no unintended compiler flags or paths are introduced; verify buildInputs for any unexpected or outdated package versions that could introduce vulnerabilities.
• Confirm no hardcoded secrets, API keys, or credentials are embedded in environment variable definitions.
• Validate that glibc development paths referenced in CFLAGS/LDFLAGS are stable and appropriate for the target platforms.

Poem

🔨 A flake arrives to build our dreams,
With Nix and Go in pristine streams,
Node and tools in harmony dance,
Dev shells unified at a glance! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add nix flake' is concise and directly describes the main change—introducing a Nix flake configuration file to the project.
Description check	✅ Passed	The description includes key required sections (PR type, rationale, issue references, and testing), though some sections are incomplete or uncertain (PR type marked as 'documentation ?').
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

flake.nix (1)

44-47: Consider whether these environment variables are necessary.

Setting GO, GOROOT, CFLAGS, and LDFLAGS manually is often unnecessary when using Nix, as the build environment typically handles these automatically. These explicit settings might cause conflicts or unexpected behavior.

If you encounter issues without these variables, they can remain. Otherwise, consider simplifying to:

           pkgs.mkShell {
             buildInputs = [
               # generic
               go-task

               # frontend
               nodejs_22
               pnpm
               nodePackages.typescript
               nodePackages.typescript-language-server

               # backend
               go
               glibc.static
               gofumpt
               golangci-lint
               sqlite
               go-swag
               gcc
               libwebp
               libavif
               libheif
               libjxl
             ];
-            CFLAGS = "-I${pkgs.glibc.dev}/include";
-            LDFLAGS = "-L${pkgs.glibc}/lib";
-            GO = "${go}/bin/go";
-            GOROOT = "${go}/share/go";
           };

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1088972 and d51d116.

⛔ Files ignored due to path filters (1)

• flake.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• flake.nix (1 hunks)

🔇 Additional comments (1)

flake.nix (1)

21-43: LGTM! Comprehensive dependency list.

The buildInputs cover all necessary tools for a full-stack development environment with Go backend, Node.js frontend, and image processing capabilities. The inclusion of both development tools (golangci-lint, gofumpt) and runtime libraries is appropriate.

[6543]

☝️ ?!?

well flake.lock is already committed and so we have master pinned ... beside as we use tools, only version bumps first land in master so there is no downside ... i would agree if we use nixos modules or lib functions that they can be "unstable" but for what we do that is totaly fine!