nixpkgs
git-lfs
nixpkgs | git-lfs | |
---|---|---|
1,020 | 162 | |
19,196 | 13,226 | |
2.9% | 0.8% | |
10.0 | 9.3 | |
3 days ago | 3 days ago | |
Nix | Go | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nixpkgs
-
Sixos: A Nix OS without systemd [video]
https://github.com/NixOS/nixpkgs/pull/372170 is a promising step towards running multiple instances of a service with separate configurations.
-
How I Use Home Assistant in 2025
That's why I asked about attitude, not anything else.
"I release my code under FOSS license, but if anyone distribute it in a way I consider not nice, I will re-license it just to screw them over." [1]
When I was considering using HA and was casually browsing community discussions, there were many posts gave me similar feeling like above case. There were other technical reasons that I decided to not to use HA, but this certainly left a really bad taste in my mouth.
1. https://github.com/NixOS/nixpkgs/pull/126326#issuecomment-86...
-
Easy development environments with Nix and Nix flakes!
Next, let's talk about what pkgs = import nixpkgs { inherit system; }; does. The import function takes in a path, and evaluates it if it is a path to a Nix file, or evaluates the default.nix file within the directory if it is a path to a directory (which is the case when a flake reference, like nixpkgs is passed to import), and returns the evaluation. Since nixpkgs points to the nixpkgs flake, which is a directory, it evaluates the default.nix file present within the flake, which in the case of nixpkgs returns a function accepting, among others, an argument for the current system, which is what we have passed to it. It then returns the set of packages for that system, which is what is bound to pkgs.
-
Nix β Death by a Thousand Cuts
I look at the Nix definition for the relevant module as you often need to see what it's actually doing in order to understand it (yes, it's one of those ecosystems).
For example, for the `steam` program (not package - the package is a dummy): https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/p... and then look for "lib.mk".
-
Getting started with Nix and Nix Flakes
lolcat is specified to the nix shell command as nixpkgs#lolcat. This is termed as an installable, and in this case, is a flake reference (more about that later). nixpkgs#lolcat is actually a URL with path nixpkgs, and fragment, i.e. the part after the #, lolcat. nixpkgs is an alias which resolves to the nixpkgs-unstable branch of the Nixpkgs GitHub repository, a vast collection of Nix packages. There are other stable branches of nixpkgs, like nixpkgs-24.11, the latest one as of writing. There are quite a few other aliases too, Nix downloads the list from this JSON file. If you omit the URL host, it defaults to the current directory (.).
-
My new Nix series!
The Nix language is used to create packages for the nix ecosystem. Nix packages, as described earlier, are built in isolation from each other, ensuring that there is no dependency hell and allows multiple versions of a package to seamlessly coexist at the same time. Nix packages are derivations: "a specification for running an executable on precisely defined input files to repeatably produce output files at uniquely determined file system paths". Nix also provides useful builtin functions and a standard environment to make packaging easier. These packages can then be shared, like any other file, and built by other people without any hassle, since Nix guarantees reproducibility. A collection of 120,000+ packages is available in the nixpkgs repository.
- Ghostty 1.0
-
Feed readers which don't take "no" for an answer
This post (before reading your comment) actually made me look into my own freshrss setup.
NixOS defaults to refresh frequency of every 5 minutes[0] (0_0).
I had noticed some blackholing me before, but never quite made the connection.
So now it is configured to fetch every 12 hours. I believe that is fair.
[0] https://github.com/NixOS/nixpkgs/blob/d70bd19e0a38ad4790d391...
-
SingleFile: A Web Extension to save a complete web page into a single HTML file
If anyone wants to help me update the nix package for the CLI, I'd appreciate it. The whole Deno thing is foreign territory for me.
https://github.com/NixOS/nixpkgs/blob/81629effd3f7e0cea0c1cf...
-
Make your QEMU 10 times faster with this one weird trick
NixOS has switched to virtiofs 4 days ago: https://github.com/NixOS/nixpkgs/pull/362081
Not all use-cases are faster with virtiofs.
git-lfs
-
Best Practices for Securing Git LFS on GitHub, GitLab, Bitbucket, and Azure DevOps
Source: git-lfs.com
-
AWS open source newsletter, #204
git-remote-s3 is a neat tool that provides you with the ability to use Amazon S3 as a Git Large File Storage (LFS) remote provider. It provides an implementation of a git remote helper to use S3 as a serverless Git server. The README provides good examples of how to set this up and example git commands that allow you to use this setup. This is pretty neat, and something I am going to try out for myself in future projects.
-
A step-by-step guide to building an MLOps pipeline
The meta-data and model artifacts from experiment tracking can contain large amounts of data, such as the training model files, data files, metrics and logs, visualizations, configuration files, checkpoints, etc. In cases where the experiment tool doesn't support data storage, an alternative option is to track the training and validation data versions per experiment. They use remote data storage systems such as S3 buckets, MINIO, Google Cloud Storage, etc., or data versioning tools like data version control (DVC) or Git LFS (Large File Storage) to version and persist the data. These options facilitate collaboration but have artifact-model traceability, storage costs, and data privacy implications.
-
Git-annex: manage large files in Git without storing the contents in Git
What's the difference between this and Git-LFS?
https://git-lfs.com/
- Twenty Years Is Nothing
-
Aho β a Git implementation in Awk
It doesn't, since Git's data model has to be changed to content-defined chunks to solve the issue.
You should look at git-lfs[1] instead.
[1] https://git-lfs.com
-
Launch HN: Diversion (YC S22) β Cloud-Native Git Alternative
Congrats on the HN launch. How does this improve or expand or blow git-lfs[1] out of the water because if I needed large blob file support it's what I would use instead. It offers pointers to the big files to the hosted git instead of pushing around the binaries itself -- though I am speculating since I've not used it myself just read about it online.
[1] https://git-lfs.com/
-
Ask HN: How do you keep your documentation, how-to, examples and blogs updated?
Specifics depend on project types, but literate programming[0] and using/enforcing coding/git/versioning standards helps. re: outdated responses -- email list for 'new/updated version available' with errata/change log location.
[0] : https://blog.bitsrc.io/literate-programming-a-radical-approa...
[1] : https://blog.codacy.com/coding-standards
[2] : https://github.com/git-lfs/git-lfs/blob/main/.github/workflo...
- Ask HN: Can we do better than Git for version control?
- We Put Half a Million Files in One Git Repository, Here's What We Learned (2022)
What are some alternatives?
zen-kernel - Zen Patched Kernel Sources
lakeFS - lakeFS - Data version control for your data lake | Git for data
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
onedrive - OneDrive Client for Linux
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
dvc - π¦ Data Versioning and ML Experiments
nixos - My NixOS Configurations
scalar - Scalar is an open-source API platform:γγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγπ Modern Rest API Clientγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγπ Beautiful API Referencesγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγγβ¨ 1st-Class OpenAPI/Swagger Support
devshell - Per project developer environments
git-fat - Simple way to handle fat files without committing them to git, supports synchronization using rsync
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
git - A fork of Git containing Windows-specific patches.