nix-prisma-example
spack
nix-prisma-example | spack | |
---|---|---|
1 | 52 | |
27 | 3,969 | |
- | 1.6% | |
0.0 | 10.0 | |
10 months ago | 5 days ago | |
Nix | Python | |
Apache License 2.0 | Apache-2.0 or MIT |
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.
nix-prisma-example
-
The Curse of NixOS
For the system, I like the devos template:
https://github.com/divnix/devos
The idea of flakes is how you define inputs, and you define the system (and packages, and shell etc.) in the outputs using the inputs. The inputs are git repos which point to other flakes. You can mix and match these as much as you want (see the devos repo for examples) and when you build the derivation, it generates a lockfile for exact commits in that point in time what were used in the given inputs.
You commit the lockfile and in the other systems where you pull your config from the repo, it uses exactly those commits and installs the same versions as you did in your other systems.
This was quite annoying and hard to do before flakes. Now it's easy.
The problem what people face with building their system as a flake is combining the packages so you can point to `jq` from the unstable nixos and firefox from the stable train. I think this aspect needs better documentation so it wouldn't be so damn hard to learn (believe me, I know). Luckily there are projects like devos that give a nice template for people to play with (with documentation!)
Another use for flakes is to create a development shell for your repo, an example what I did a while ago:
https://github.com/pimeys/nix-prisma-example
Either have `nix-direnv` installed, enter the directory and say `direnv allow`, or just `nix develop` and it will gather, compile and install the correct versions of packages to your shell. Updating the packages? Call `nix flake update` in the directory, commit the lockfile and everybody else gets the new versions to their shell.
spack
-
Autodafe: "freeing your freeing your project from the clammy grip of autotools."
> Are we talking about the same autotools?
Yes. Instead of figuring out how to do something particular with every single software package, I can do a --with-foo or --without-bar or --prefix=/opt/baz-1.2.3, and be fairly confident that it will work the way I want.
Certainly with package managers or (FreeBSD) Ports a lot is taken care of behind the scenes, but the above would also help the package/port maintainers as well. Lately I've been using Spack for special-needs compiles, but maintainer ease also helps there, but there are still cases one a 'fully manual' compile is still done.
> Suffice it to say, I prefer to work with handwritten makefiles.
Having everyone 'roll their own' system would probably be worse, because any "mysteriously failure" then has to be debugged specially for each project.
Have you tried Spack?
* https://spack.io
* https://spack.readthedocs.io/en/latest/
-
FreeBSD has a(nother) new C compiler: Intel oneAPI DPC++/C++
Well, good luck with that, cause it's broken.
Previous release miscompiled Python [1]
Current release miscompiles bison [2]
[1] https://github.com/spack/spack/issues/38724
[2] https://github.com/spack/spack/issues/37172#issuecomment-181...
-
Essential Command Line Tools for Developers
gh is available via Homebrew, MacPorts, Conda, Spack, Webi, and as a…
-
The Curious Case of MD5
> I can't count the number of times I've seen people say "md5 is fine for use case xyz" where in some counterintuitive way it wasn't fine.
I can count many more times that people told me that md5 was "broken" for file verification when, in fact, it never has been.
My main gripe with the article is that it portrays the entire legal profession as "backwards" and "deeply negligent" when they're not actually doing anything unsafe -- or even likely to be unsafe. And "tech" knows better. Much of tech, it would seem, has no idea about the use cases and why one might be safe or not. They just know something's "broken" -- so, clearly, we should update.
> Just use a safe one, even if you think you "don't need it".
Here's me switching 5,700 or so hashes from md5 to sha256 in 2019: https://github.com/spack/spack/pull/13185
Did I need it? No. Am I "compliant"? Yes.
Really, though, the main tangible benefit was that it saved me having to respond to questions and uninformed criticism from people unnecessarily worried about md5 checksums.
- Spack Package Manager v0.21.0
- Show HN: FlakeHub – Discover and publish Nix flakes
-
Nixhub: Search Historical Versions of Nix Packages
[1] https://github.com/spack/spack/blob/develop/var/spack/repos/...
-
Cython 3.0 Released
In Spack [1] we can express all these constraints for the dependency solver, and we also try to always re-cythonize sources. The latter is because bundled cythonized files are sometimes forward incompatible with Python, so it's better to just regenerate those with an up to date cython.
[1] https://github.com/spack/spack/
-
Linux server for physics simulations
You want to look at the tools used for HPC systems, these are generally very well tried and tested and can be setup for single machine usage. Remote access - we use ssh, but web interfaces such as Open On Demand exist - https://openondemand.org/. For managing Jobs, Slurm is currently the most popular option - https://slurm.schedmd.com/documentation.html. For a module system (to load software and libraries per user), Spack is a great - https://spack.io/. You might also want to consider containerisation options, https://apptainer.org/ is a good option.
-
Simplest way to get latest gcc for any platform ?
git clone https://github.com/spack/spack.git ./spack/bin/spack install gcc
What are some alternatives?
nixos-beginners-handbook - The missing handbook for NixOS beginners
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
impermanence - Modules to help you handle persistent state on systems with ephemeral root storage [maintainer=@talyz]
nixpkgs - Nix Packages collection & NixOS
star-history - The missing star history graph of GitHub repos - https://star-history.com
nix-processmgmt - Experimental Nix-based process management framework
asdf-nodejs - Node.js plugin for asdf version manager
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
aconfmgr - A configuration manager for Arch Linux
ohpc - OpenHPC Integration, Packaging, and Test Repo
nixpkgs-config - ~/.config/nixpkgs
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container