You are not logged in.
Hello Arch Linux Community!
I'd like to share a small project I've been working on: **Trizen-Remote**.
**What's the goal?**
The idea is simple: to allow offloading the compilation load of AUR (Arch User Repository) packages to a remote machine (a server, a more powerful PC) via SSH, while keeping the user experience on the local machine as close as possible to the classic `trizen`. This is particularly useful if your desktop/laptop is a bit resource-constrained for large compilations.
I'm just using a LXC container with Manjaro or ArchLinux on my proxmox.
**How does it work?**
The system consists of two main scripts:
1. **`trizen-remote` (on your local machine)**:
* This script is used exactly like `trizen` (`trizen-remote -S package_name`, `trizen-remote aur_package_name`, etc.).
* It reads a simple configuration file (`~/.config/trizen-remote/config.conf`) for SSH connection details to your server.
* It forwards the `trizen` command to the server script.
* The output from the remote `trizen` (including interactive dialogues for package selection or PKGBUILD editing) is displayed in real-time on your local terminal.
* Once an AUR package is built on the server (without being installed there), it's automatically transferred back to your local machine via SCP/SFTP.
* `trizen-remote` then installs the received package on your local machine using your local `trizen` (`trizen -U`).
2. **`trizen-server-handler.sh` (to be placed on your server machine)**:
* This script receives the command from `trizen-remote`.
* It executes `trizen` in a temporary directory, ensuring AUR packages are only built (`--buildonly`, `--noinstall`) and not installed on the server.
* It handles client IP detection (via `SSH_CLIENT`) for returning the package.
**Key Features:**
* **Transparent User Experience**: Use `trizen-remote` just like `trizen`.
* **Preserved Interactivity**: Dialogues for package selection, PKGBUILD editing, etc., work across the SSH session.
* **Configurable Interactivity Mode**: You can configure in `~/.config/trizen-remote/config.conf` whether server operations should always be interactive, never interactive (`--noconfirm`), or if the script should prompt you each time.
* **Internationalization (WIP)**: Script messages are being translated (English, French, Spanish, Italian, German, Portuguese) and adapt to your system's language.
* **Syntax Highlighting**: Script messages use colors for better readability, similar to `trizen`'s output.
This is an proof of concept version. Feel free to fork and improve.
I hope this tool can be useful to some of you.
Thanks!
Where to download scripts : https://github.com/trizen/trizen/issues/261
Offline
Moderator Note
Moving to Community Contributions
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline