π‘
RLXOS utilizes a temporary lightweight bwrap container to isolate the build process of each component from the system, ensuring no alterations are made to your system in any way.
## Obtaining Source Code
Simply fork my GitHub repository at [https://github.com/itsManjeet/rlxos/](https://github.com/itsManjeet/rlxos/) containing the meta-configuration files for building RLXOS. Your star would be much appreciated to support my work.
If you're not on GitHub, clone the project using:
```bash
git clone --recurse-submodules --branch stable https://github.com/itsManjeet/rlxos
```
## Project Structure
| File/Folder | Description |
| --- | --- |
| elements/ | YAML configuration files for each component |
| files/ | Files required by one or more components to build, such as icons, service files, background wallpaper, or logos. |
| patches/ | Patch files used for fixes or customization of each component. |
| scripts/ | Scripts utilized in CI/CD pipelines. |
| config-<ARCH>.yml | Project configuration file used by Ignite to set up environment variables, provide global variables, and compiler information. |
| include/ | Shared configurations imported in config-<ARCH>.yml |
## Ignite! the build processπ₯
Now that we have the source code, let's build our first RLXOS distribution. You'll understand why I call it Ignite! the build process later.
Firstly, create your own GPG key to sign the updates
Begin by removing the default rlxos.gpg key:
```bash
rm -v files/rlxos.gpg
```
Then generate a new one:
```bash
make file/rlxos.gpg
```
This action will create a public key at `files/rlxos.gpg` and a private key at `ostree-gpg/`. The private key is utilized to sign the OTA updates, while the public key is provided to users within the release ISO to verify OTA updates.
Execute:
```bash
make ELEMENT=installer/image.yml
```
Now, sit back and watch HIMYM to know how Ted meets his children's mother. Yes, it may take that long (unless you're Barney with NASA's hardware).