Would it make sense to start a repo which contains some "standard" flake.nix files for various types of projects?

• templates

  10 365 6.0 Nix

  Flake templates (by NixOS)

  

• templates

  1 37 7.7 Nix

  Nix flake templates managed by the community [maintainer=@IogaMaster] (by nix-community)

  

Also, I see that it suggests this for "more advanced" usages but there's literally nothing there: https://github.com/nix-community/templates

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• nix-beam-flakes

  1 36 9.2 Nix

  Discontinued Nix-based BEAM toolchain management

I left it vague because I didn't want to seem self-promotional. Unmerged documentation branch is the best starting place here: README, docs folder of that branch, example from develop. I daily drive it at work, and on a personal project for about 8 months. Doesn't do well for monorepos with disparate BEAM versions yet, but there are escape hatches and usage-as-library too. For the typical Phoenix project with a few extra system deps it's a pretty good onramp. perSystem.beamWorkspace.devShell.extraPackages is how you add arbitrary buildInputs like your VIPS stuff and .extraArgs for additional arguments to mkShell, such as your non-sensitive envvars. There's a page for future goals too. Publishing the rendered docs as a static site is in my TODOs, it's mostly glue left.

Suggest a related project