29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# mikroskeem's AUR build bot
|
|
|
|
NOTE: This is actually not ready, so it is not recommended to run it in production (don't be like me!)
|
|
|
|
## Installing
|
|
|
|
* Set up new Arch Linux nspawn container (I recommend using this [script](https://gist.github.com/artizirk/fab2ce13277a190ee6063b03b8e0a6e9) made by @arti)
|
|
* Install [aurutils](https://aur.archlinux.org/packages/aurutils) and set it up
|
|
* Copy `buildpkg` to `/usr/bin` in builder container
|
|
* Set up [OpenSMTPD](https://wiki.archlinux.org/index.php/OpenSMTPD) server on container and host (to send emails to builder in case of failure)
|
|
- Note: Don't forget to firewall!
|
|
* Copy `aur` script to `/usr/bin` in host machine
|
|
* Set up nginx to serve packages to host (and maybe for public)
|
|
* Take look at `scripts/` directory, you might find useful scripts there
|
|
|
|
## Known issues
|
|
* You can't edit PKGBUILD-s
|
|
* You can't accept GPG keys automatically (insecure to do so, but you can do `gpg --recv-key <key>` in container shell)
|
|
* Not documentated enough!
|
|
* Probably something more I'm not currently aware of
|
|
* Storing GPG password is insecure, if your builder gets hacked, then revoke your key
|
|
|
|
## TODO
|
|
* Pacman cache automatic cleanup timer
|
|
* AUR build data automatic cleanup
|
|
|
|
## More ideas
|
|
* Telegram Bot to build packages?
|