nixpacks
nickel
nixpacks | nickel | |
---|---|---|
17 | 46 | |
2,144 | 2,153 | |
3.8% | 2.8% | |
8.7 | 9.5 | |
4 days ago | 1 day ago | |
Rust | Rust | |
MIT License | MIT License |
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.
nixpacks
-
9 ways to improve how you ship software
Example with Nixpacks:
-
Multi-Worker Application on ARM Architecture
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.
-
Using Nix with Dockerfiles
I think this is something the writer of the article would be delighted to find: https://github.com/railwayapp/nixpacks
-
[Media] Gitrun: Run any Git repository with one command
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 .
- Show HN: IHP v1.0 (Batteries-included web framework built on Haskell and Nix)
-
We want to make Nix better
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.
-
A selfhosted Heroku clone on your Kubernetes cluster
Hey! Any plans on integrating nixpacks? I'm one of the core maintainers & would love to help you out. No worries if not.
- Nixpacks takes a source directory and produces an OCI compliant image
-
Deploying Strapi 4 to Railway
Uses NixPacks to build the images;
nickel
-
Nix – A One Pager
So, its key features are:
1. domain-specific: designed for conveniently creating and composing derivations. This reason alone already justifies a new language, or an embedded domain-specific language (such as the Guile/Scheme for guix), or a mix of both (Starlark, the build language of Bazel embedded in a restricted Python-variant).
2. purely functional: this ties well into the philosophical backing of Nix the package manager, which aims to be purely functional, also known as hermeticity in other build systems (Bazel).
3. lazily evaluated: similar to other build systems (including Bazel), so that you can build only what you need on demand.
4. dynamically typed: this one is controversial. Being dynamically typed—in other words, not developing a type system—gets Nix out of the door first. But users often complain about the lack of proper types and modularity. There are experiments to address this, such as Nickel (https://github.com/tweag/nickel).
It is understandable that a one-pager may not have space for the whys.
-
10 Ways for Kubernetes Declarative Configuration Management
Nickel:Nickel is a straightforward configuration language aimed at automatically generating static configuration files. Essentially, it's akin to JSON with the addition of functions and types.
-
Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
Also look at nickel which is an evolution of nix. It's my favorite in this space.
nickel-lang.org
https://github.com/tweag/nickel
- Show HN: Flake schemas – teaching Nix about your flake outputs
-
What config format do you prefer?
Or this https://github.com/tweag/nickel
-
Nickel 1.0
Nickel is a programming language. While HCL is just a configuration format, so not really comparable.
Here's a comparison with similar tools: https://github.com/tweag/nickel#comparison
-
Announcing Nickel 1.0, a configuration language written in (and usable from) Rust
As for 'providence', I suppose you meant provenance :) it's been delayed because this was less critical for 1.0 to decide on or to implement (as it: it doesn't break backward compatibility in any way to add this feature in the short term), but this is very much on the roadmap: Issue #235. That's a must-have in a language with merging like Nickel.
-
Rewrite it in Rust: Kubernetes
Have you considered using a different language for templating? this could be a BIG selling point. Some good ones are cue-lang (though I haven't seen support for rust), kcl or nickel-lang.
- Nickel v1.0.0
- Design rationale for the Nickel configuration language
What are some alternatives?
sidekiq - Sidekiq worker on Render
rnix-lsp - WIP Language Server for Nix! [maintainer=@aaronjanse]
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
nixos - My NixOS Configurations
cog - Containers for machine learning
nix-gui - Use NixOS Without Coding
heroku-deploy - A simple github action that dynamically deploys an app to heroku
nix-doc - An interactive Nix documentation tool providing a CLI for function search, a Nix plugin for docs in the REPL, and a ctags implementation for Nix script
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
AppImageKit - Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
engine - The Orchestration Engine To Deliver Self-Service Infrastructure Faster ⚡️
nix - Nix, the purely functional package manager