base on Immutable infrastructure for the desktop! <p align="center"> <img src="https://raw.githubusercontent.com/goldboot/goldboot/master/.github/images/goldboot-256.png" /> </p>   [](https://discord.gg/Vzr7gT5dsd)  [](https://turbine.goldboot.org)  <hr> People usually don't reinstall their OS from scratch very often. When they do, chaos ensues the moment they reach that pristine desktop or terminal. Settings get changed, applications are installed, bloatware is removed, files are downloaded here and there. The system is generally altered from its original state into a new "customized" state by a manual flurry of mouse clicks and key presses. This standard approach is like _mutable infrastructure_, meaning you mutate the state of your system repeatedly until it eventually suits your needs. And when something goes awry, you have to make the necessary changes to get it back in line. For most people, mutable infrastructure works out fine until something major breaks or they have to migrate to a new computer altogether. In these cases, they probably end up starting over from scratch and reapply their changes again (and probably slightly differently this time). Sophisticated computer elites probably practice _immutable infrastructure_. Meaning that, every time they boot their system, its state begins almost identically to the time before. Any changes that are made during the course of runtime vanish on reboot. This approach has some real benefits, but requires quite a bit of effort from the user. `goldboot` is a tool that builds machine images for real hardware that can help you achieve something close to immutable infrastructure without creating a lot of extra work for yourself. In the `goldboot` approach, you create a declarative configuration file for each machine that you want to deploy. Using this configuration, `goldboot` builds an image either on your local machine or on a CI platform like Github Actions. The resulting image can be deployed to real hardware via a USB drive or through PXE boot. **Warning: this tool is totally unfinshed and should be used for testing only! Proceed at your own risk!** <hr> <p align="center"> <img src="https://raw.githubusercontent.com/goldboot/goldboot/master/.github/images/overview.png" /> </p> `goldboot` is approximately what you would get if [`docker`](https://www.docker.com) and [`packer`](https://www.packer.io) were mixed together. Instead of building containers or virtual machines, `goldboot` builds images for real hardware. These machine images (also known as _golden images_) contain your operating system(s), applications, software patches, and configuration all rolled into one easily deployable package. Like Docker images, your `goldboot` images can be stored in a registry and pulled onto real hardware. ## Installation <details> <summary>Docker</summary>    #### Install from DockerHub ```sh alias goldboot="docker run --rm -v .:/root fossable/goldboot" ``` </details> <details> <summary>Crates.io</summary>  #### Install from crates.io ```sh cargo install goldboot ``` </details> <details> <summary>Arch Linux</summary>    #### Install from the AUR ```sh cd /tmp curl https://aur.archlinux.org/cgit/aur.git/snapshot/goldboot.tar.gz | tar xf - makepkg -si ``` </details> <details> <summary>Github Releases</summary>  #### Install manually from Github releases ```sh curl -o /usr/bin/goldboot https://github.com/fossable/goldboot/releases/download/goldboot-v0.0.7/goldboot_<platform> chmod +x /usr/bin/goldboot ``` ##### Dependencies ```sh apt-get install -y libudev1 libgtk-4-1 libglib2.0-0 ``` </details> <details> <summary>Github Actions</summary> #### Running on Github actions Building golden images with CI is common practice, so there's also a [Github action](https://github.com/fossable/goldboot-action) to make it easy: ```yml steps: - name: Checkout uses: actions/checkout@v4 - name: Build goldboot image uses: fossable/goldboot-action@main with: config-path: goldboot.json output-path: image.gb - name: Save image artifact uses: actions/upload-artifact@v3 with: name: my_image.gb path: image.gb ``` </details> ## Examples The [goldboot-examples](https://github.com/fossable/goldboot-examples) repo contains example configurations of all supported OS types and system architectures. They are built on a weekly schedule against the latest version of `goldboot`. | Linux | Windows | macos | | ----- | ------- | ----- | |   |   |   | |   | | |   | | |   | | |   | | |   | | ## Example walkthrough Let's build a basic Arch Linux  image to prove we're _real_ Linux users. First, create a directory to hold our configuration (which can later be tracked in version control): ```sh mkdir Test && cd Test ``` Initialize the directory and choose `ArchLinux` to start with: ```sh goldboot init \ --name Test \ --os ArchLinux \ --size 10G \ --format json ``` This will create `goldboot.json` which contains configuration options that can be tweaked to suit your needs. For example: ```json { "alloy": [ { "os": { "ArchLinux": { "hostname": "YeahIUseArch", "root_password": { "plaintext": "123456" } } }, "source": { "Iso": { "url": "https://mirrors.edge.kernel.org/archlinux/iso/2024.01.01/archlinux-2024.01.01-x86_64.iso", "checksum": "sha256:12addd7d4154df1caf5f258b80ad72e7a724d33e75e6c2e6adc1475298d47155" } } } ], "arch": "Amd64", "name": "Test", "size": "10G" } ``` There are many ways to customize the image, but for now just build it: ```sh goldboot cast . ``` Once the build succeeds, the image will be saved to the system's library directory. To deploy it to a physical disk, you can include the image on a new bootable USB drive: ```sh # THIS WILL OVERWRITE /dev/sdX! goldboot liveusb --output /dev/sdX --include Test ``` Once the USB is created, you can use it to boot into the goldboot live environment and select an image to deploy: <p align="center"> <img src="https://raw.githubusercontent.com/goldboot/goldboot/master/.github/images/select_image.png" /> </p> Once the image has been deployed, remove the bootable USB drive and reboot the machine. ", Assign "at most 3 tags" to the expected json: {"id":"10136","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"