stage0
nixpacks
stage0 | nixpacks | |
---|---|---|
22 | 17 | |
888 | 2,144 | |
- | 3.0% | |
3.9 | 8.7 | |
3 months ago | 3 days ago | |
Assembly | Rust | |
GNU General Public License v3.0 only | 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.
stage0
- Running the "Reflections on Trusting Trust" Compiler
- Stage0: A minimal bootstrapping path to a C compiler capable of compiling GCC
- Goodbye to the C++ Implementation of Zig
- Stage0 – A set of minimal dependency bootstrap binaries
-
Nixpacks takes a source directory and produces an OCI compliant image
Somewhat tangential, but I'm curious how big the bootstrap seed for Nix is. That is, if you wanted to build the entire world, what's a minimum set of binaries you'd need?
Guix has put quite a bit of work into this, AFAIU, and it's getting close to being bootstrappable all the way from stage0 [0]. Curious if some group is also working on similar things for Nix.
[0]:https://github.com/oriansj/stage0
-
"Do you believe that every upstream project... is examined by an expert who can accurately identify whether said project contains malware...?"
https://www.bootstrappable.org/ has some good info. Reading the source of https://github.com/oriansj/stage0 is also very enlightening. It's set its goal to be understandable by 70% of programmers.
- Stage0 - A set of minimal dependency bootstrap binaries
-
Common libraries and data structures for C
Even if they aren't, people absolutely should be able to bootstrap new platforms from scratch. It's important to have confidence in our tools, in our ability to rebuild from scratch, and to be safe against the "trusting trust" attack among other things.
Lately I've been catching up on the state of the art in bootstrapping. Check out the live-bootstrap project. stage0 starts with a seed "compiler" of a couple hundred bytes that basically turns hex codes into bytes while stripping comments. A series of such text files per architecture work their way up to a full macro assembler, which is then used to write a mostly architecture-independent minimal C compiler, which then builds a larger compiler written in this subset of C. This then bootstraps a Scheme in which a full C compiler (mescc) is written, which then builds TinyCC, which then builds GCC 4, which works its way up to modern GCC for C++... It's a fascinating read:
https://github.com/oriansj/stage0
https://github.com/fosslinux/live-bootstrap/blob/master/part...
Even if no one is "using" this it should still be a primary motivator for keeping C simple.
-
How To Build an Evil Compiler
One countermeasure not mentioned here is bootstrapping a compiler with a program small enough to be manually verified. The stage0 project is under 1KB (small enough that the binary can be, and has been, manually checked against the hand written assembly), and GNU Guix (a system for reproducible, isolated builds) is currently working on moving it's bootstrap speed to stage0. That means that, fairly soon, there will be a large set of software that doesn't have a connection to an original C compiler.
- A minimal C compiler in x86 assembly
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;
What are some alternatives?
rizin - UNIX-like reverse engineering framework and command-line toolset.
sidekiq - Sidekiq worker on Render
arocc - A C compiler written in Zig.
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
chibicc - A small C compiler
cog - Containers for machine learning
libcperciva - BSD-licensed C99/POSIX library code shared between tarsnap, scrypt, kivaloo, spiped, and bsdiff.
heroku-deploy - A simple github action that dynamically deploys an app to heroku
bug - Scala 2 bug reports only. Please, no questions — proper bug reports only.
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
c4 - C in four functions
engine - The Orchestration Engine To Deliver Self-Service Infrastructure Faster ⚡️