nix-ld VS nixpacks

You may be interested in `nix-ld`. https://github.com/Mic92/nix-ld

As I mentioned I used nix-index to build LD_LIBRARY_PATH. I believe I picked that up from nix-ld. The README on that page shows an example and mentions some tools (nix-autobahn, nix-alien, and nix-index) to help figure it out.

Hi guys, I really like NixOS. I also do not want to miss nix-ld, because it allows me to run "normal" Linux programs on nix.

As someone who has been using NixOS for a couple of years now, I really want to say how appreciative I am of everybody for making noticeable improvements to the system on a somewhat regular basis. The nix command keeps on adding great new features like flake templates and bundling as well as just being more user friendly (error messages, actionable hints, etc.) Additionally, tools like nix-ld [1] make nix more usable than ever with software from external sources. Things just keep on getting better for NixOS users!

Despite the reputation, I feel that NixOS or some derivative of it has the power to become the best distribution for non-technical users in the long run. What NixOS has done is effectively built an interface to every component of a modern Linux system, all that needs to be built is a user application to take advantage of it. Of course, there still needs be some improvements in Nix itself for it to blossom into its final form, but I really see a path to greatness here.

I have often thought about creating a simple unified Win2K-esq or BeOS-like X11 WM/DE specifically for NixOS but unfortunately I like the time/motivation.

[1] https://github.com/Mic92/nix-ld

Regarding the ld thing, I don't know if this is relevant but probably: https://github.com/Mic92/nix-ld

Have a look at nix-ld and nix-autobahn.

Example with Nixpacks:

We have an upcoming nixpacks builder that should work on ARM/ARM64, but there are issues in the nixpacks codebase I'm still trying to sort out before that lands.

I think this is something the writer of the article would be delighted to find: https://github.com/railwayapp/nixpacks

Yes, it builds the Dockerfile if it exists otherwise it uses nixpacks to create an image from source files for any language/framework. This image is then run using docker run .

I think this is true for Nix in the deployment/ops space, where debugging a broken build can be very frustrating. Language improvements are going to be less useful for app developers, the Flake learning curve is not going to get better with a type system.

Perhaps something like heroku buildpaks (https://github.com/railwayapp/nixpacks ?) would help devs get on the Nix train.

Hey! Any plans on integrating nixpacks? I'm one of the core maintainers & would love to help you out. No worries if not.

Uses NixPacks to build the images;