archinstall
nix
Our great sponsors
archinstall | nix | |
---|---|---|
199 | 366 | |
5,521 | 10,621 | |
2.4% | 7.1% | |
9.4 | 10.0 | |
12 days ago | 1 day ago | |
Python | C++ | |
GNU General Public License v3.0 only | GNU Lesser General Public License v3.0 only |
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.
archinstall
-
Endeavor vs Vanilla arch?
The related issue https://github.com/archlinux/archinstall/issues/1111 implies it's fixed, but either way, you can just securely delete your password after the install.
-
Does Archinstall have any downsides?
Still feels that it is in rapid development phase, rather than just maintenance, last month I encountered this bug
-
"Failed to install packages to new root\r\n" (Archinstall script)
The problem has been fixed in Git, we'll just have to wait for the fix to be released in the next version of archinstall.
- I need some help with archinstall...
-
What login manager is this
According to Archinstall's code, it seems like the bspwm profile installs lightdm by default
- Update to Linux install script (ArchLinux Edition)
-
Arch server ?
If you use a configuration file and don't use custom-commands, there is no problem whatsoever. I do believe Archinstall's developers are going to make sure no declaration will fail. That being said, looking at their bug tracker, it looks like Arch is moving a bit too fast for them too as there are installation-blocking bugs regularly showing up (and usually solved swiftly!) but do you want to wait for 2 months to redeploy your system your secondary disk is confusing the installer?
-
Can i find the script of Archinstall?
reading https://github.com/archlinux/archinstall or just read the arch installation wiki is pretty much just does that
The archinstall script source code can be found on GitHub/archlinux/archinstall.
nix
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Go + Hypermedia - A Learning Journey (Part 1)
1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity
-
What it was like working for Gitlab
Semi-related, I would recommend to anyone who is a Linux native to try to find some kind of "minimum viable setup" that is really really easy for you to run out of VirtualBox or Parallels or something for this reason. No matter where you go, you know you can have a suite of tools which work just as you want them to there. Being able to tear it down and rebuild it quickly is also a great way to deal with debugging certain kinds of problems of the "it runs/doesn't run on my machine" category.
How you do this is of course up to you. At one end of the spectrum is just relying on your memory. At the other end is using NixOS https://nixos.org/ to get fully reproducible builds anywhere you go. Between these are a vast field of options. I know a guy who maintains an Ansible file set to `host: localhost` which installs everything he wants from that file. For me, I just stick with the latest Ubuntu version and maintain a few shell scripts [1] that install 80% of what I like to have on a new install.
If you like the scientific approach, you can install something like https://atuin.sh/ and do some statistics on what programs you actually run most frequently based on your long term shell history.
-
Cloudflare R2-Backed Nix Binary Cache on Fly.io
See https://github.com/NixOS/hydra/issues/838 for making content-addressed derivations supported by hydra.nixos.org. At that point, we can actually try out the XP feature at scale.
Also see https://github.com/NixOS/nix/issues/8919 for this accepted RFC
Once those things are done, we can get back to merging in the IPFS code.
Now that there is an Nix team and I am on it, there is much, much less of an issue of these experiments being caught in limbo :).
-
The one thing I do not like about the Nix package manager (and a fix for it)
The nix package manager is an awesome package manager for linux and macos, which focuses on declarative packages. This means that you can dump out all the packages you want into a file, and nix will go out and fetch them for you.
- NixOS: Declarative Builds and Deployments
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
-
How I use Nix in my Elm projects
Nix is a tool that allows you to make reproducible development environments. I've started using it in all my Elm side projects and I've had a good experience with it thus far. To pique your curiosity I just wanted to share my simple setup that has been working quite well for me.
-
Shopware Changes since the 6.0 Dev Training Videos
The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."
What are some alternatives?
archfi - Arch Linux Fast Installer : tutorial installer
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
void-packages - The Void source packages collection
flatpak - Linux application sandboxing and distribution framework
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
Ventoy - A new bootable USB solution.
guix - Read-only mirror of GNU Guix — pull requests are ignored, see https://guix.gnu.org/en/manual/en/guix.html#Submitting-Patches instead
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container
archiso - Official archiso scripts Repository (read-only mirror)
build-emacs-for-macos - Somewhat hacky script to automate building of Emac.app on macOS.
nix-darwin - nix modules for darwin