/explore
|
You are here 
|
blog.ysndr.de | ||
| | | | |
www.smartjava.org
|
|
| | | | | Managing runtime dependencies using NixWe're setting up a new project at work, and wanted to apply some lessons learned from previous projects. One of the things we ran into was that when onboarding new people, or setting up a new development environment on a different machine, the dependencies were sometimes out of sync. Usually this was quite easy to fix, but keeping all the versions in sync, and dealing with deprecated or not working features (e.g terraform or kustomize) quickly becomes very annoying.Recently we ran into another issues where a newer version of java caused issues, which led to a new version of gradle, which meant updating our build files etc. While not an issue in itself, and something that we had to do eventually, but we didn't really pla... | |
| | | | |
serokell.io
|
|
| | | | | Learn how the Nix package manager can help you make the development process more efficient and simpler. | |
| | | | |
www.zombiezen.com
|
|
| | | | | I recently spent some time learning Nix after watching this talk by Xe. Nix is a package manager/build system for Linux and macOS. It does a number of things I really like: Transparent handling of source and binary packages. Includes a rich central package registry, but you can host your package descriptions or binaries anywhere. Does not require root and runs alongside any Linux distribution. Easy to pin or customize versions of individual packages. Straightforward support for project-specific dependenc... | |
| | | | |
newcome.wordpress.com
|
|
| | | I'm a little slow on the uptake with version management of language runtimes and environments. For a long time I just followed the Linux distribution convention of global versions of dependencies and compiler versions for my system. This changed during my years doing NodeJS development where the language and tools were changing daily it seemed.... | ||
