altercation/archblocks là dự án mã nguồn mở trên GitHub với 139 sao, viết chủ yếu bằng Shell. Arch Linux Modular Install Script
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
ArchBlocks - a minimal, modular, manual install framework
WHAT:
ArchBlocks is a very lightweight framework for creating quick, modular, non-interactive Arch Linux install scripts tailored to specific systems. It is accessible via a single quick curl downloadable script (from, for example, github).
WHERE:
Example repo at https://github.com/altercation/archblocks
Arch BBS: https://bbs.archlinux.org/viewtopic.php?id=149597
EXAMPLE:
Boot Arch install media (in the example config I expect an EFI boot, but it's trivial to make this work for non EFI):
(this then sources the blocks of code remotely and configures the system based on the specific blocks called and variables set in in; see below)
WHAT IT ISN'T:
ArchBlocks is not an interactive general purpose script that asks you what you'd like. You must customize it (or its blocks) as much as any other install script. ArchBlocks simply makes this process easier to maintain as a single project that is applicable for multiple systems.
WHY:
Many somewhat experienced Arch users end up building lightweight install scripts to set up their systems. I've been wanting to modularize my own install scripts such that multiple, different system types (laptop/server/desktop/headless) can reuse most of the common elements easily and swap out blocks of code as needed.
AND YET it's easy to make something like this far too complex. To paraphrase the Ruby community: Arch is Simple so Our Utilities Are Simple. ArchBlocks kickstarts off a single "configuration" script and loads blocks from a single directory (remote or local, doesn't matter).
(I've previously written extensive additions to AIF before it was frozen in carbonite, and that experience convinced me of the value of a non-interactive, simple install script based approach).
NO REALLY, WHY NOT JUST MONOLITHIC INSTALL SCRIPTS, WHY MODULAR:
There is install code that may be impacted by changes to Arch, or I sometimes want to improve the way I handle some part of the installation. This may impact multiple systems. Rather than update and maintain five different manual install scripts, modular is better approach. A simple example is the various NETWORK_* blocks. I can keep using the default network setup method in most of my scripts and use a light weight / minimal network install method by just swapping out a block. This minimal install script can be revised and all systems that I install with it in future will make use of the revision.
BUT INSTALLING ARCH IS EASY
It is. It's mostly the filesystem and bootloader varieties which create complexity for me. This addresses that.
Another benefit of this modular approach is I can include post-flight app installation a per machine basis (my server gets nginx, my laptop gets dwarffortress). All automated.
DETAILS:
Each system I install gets a single config file (the "tau" script in the example above is a laptop). This script loads a few very lightweight helper functions (maintained in a lib file for reuse across "config" scripts) and then loads blocks from the (surprise) blocks directory (local or remote). These blocks are almost all just simple blocks of bash script. The only exceptions should be very clear from the example: there are a few functions that are very specific to the filesytem configuration that must be sprinkled throughout the code. These functions and their intended sequence in the script are easily identified by name such as FILESYSTEM_PRE_BASEINSTALL (in this case FILESYSTEM_PRE_BASEINSTALL is either a null function or does something as defined in the FILESYSTEM block).
A config/install script (the only script you need to manually execute) looks like this (actual script I use to install Arch on a Thinkpad x220):
The blocks subdirectory (the only subdirectory used) contains blocks of simple bash script and looks something like this (note the variants in items like NETWORK... I am working on alternates for FILESYSTEM and BOOTLOADER as well, but the principle should be clear)::
altercation/archblocks có 139 sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/altercation/archblocks. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
altercation/archblocks có tag gì không?
Bản đồng bộ chưa ghi nhận topic GitHub nào cho altercation/archblocks. GitHub topics hiển thị ở thanh bên phải trang repo — đó là nơi đáng kiểm tra nhất.
altercation/archblocks có website riêng không?
TopGit chưa ghi nhận URL trang chủ cho altercation/archblocks. Phần README ở tab phía trên thường có link demo, hoặc xem mô tả GitHub của repo.
altercation/archblocks còn đang phát triển không?
Commit gần nhất trên altercation/archblocks là 5.5 năm trước (theo timestamp GitHub). Repo có 34 fork — một chỉ báo về mức độ quan tâm của cộng đồng.
altercation/archblocks viết bằng ngôn ngữ gì?
altercation/archblocks chủ yếu viết bằng Shell. Trường "language" của GitHub dựa trên phần lớn byte ở nhánh mặc định.
Đọc thêm về altercation/archblocks ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/altercation/archblocks là nguồn chính thức.
Đọc đầy đủ README ở tab phía trên.
Muốn nghe thêm một ý kiến về archblocks?
Hỏi một AI đọc được trang này — một cú bấm là có ngay nhận định về archblocks.