forked from vieter-v/vieter
Added README
parent
9d1587337f
commit
9a09db0485
|
@ -0,0 +1,23 @@
|
||||||
|
# Vieter
|
||||||
|
|
||||||
|
Vieter is a re-implementation of the Pieter project. The goal is to create a
|
||||||
|
simple PKGBUILD-based build system, combined with a self-hosted Arch
|
||||||
|
repository. This would allow me to periodically re-build AUR packages (or
|
||||||
|
PKGBUILDs I created myself), & make sure I never have to compile anything on my
|
||||||
|
own systems, making my updates a lot quicker.
|
||||||
|
|
||||||
|
## Why V?
|
||||||
|
|
||||||
|
I chose [V](https://vlang.io/) as I've been very intrigued by this language for
|
||||||
|
a while now. I wanted a fast language that I could code while relaxing, without
|
||||||
|
having to exert too much mental effort & V seemed like the right choice for
|
||||||
|
that.
|
||||||
|
|
||||||
|
## Features
|
||||||
|
|
||||||
|
The project will consist of a server-agent model, where one or more builder
|
||||||
|
nodes can register with the server. These agents communicate with the Docker
|
||||||
|
daemon to start builds, which are then uploaded to the server's repository. The
|
||||||
|
server also allows for non-agents to upload packages, as long as they have the
|
||||||
|
required secrets. This allows me to also develop non-git packages, such as my
|
||||||
|
terminal, & upload them to the servers using CI.
|
Loading…
Reference in New Issue