Chewing_Bever
/
vieter
forked from vieter-v/vieter
1
0
Fork 0
Code Issues Pull Requests Releases Activity
My development fork of Vieter.
11 Commits
13 Branches
3 Tags
3.1 MiB
V 88.3%
Shell 6.1%
Python 3.4%
Makefile 1.3%
Dockerfile 0.7%
Other 0.2%
 
 
 
 
 
 
Go to file
Jef Roosens 93c0dc9c4f
Added start of repo-add functionality 		2022-01-09 22:30:07 +01:00
vieter Added start of repo-add functionality 2022-01-09 22:30:07 +01:00
.dockerignore Added Dockerfile & beginning of vweb server 2022-01-09 09:29:11 +01:00
.gitignore Started logging stuff; added vweb source code 2022-01-09 17:44:47 +01:00
.woodpecker.yml Switched CI to vieter name 2022-01-09 09:30:45 +01:00
Dockerfile Added Dockerfile & beginning of vweb server 2022-01-09 09:29:11 +01:00
Makefile Started own mod of vweb library; first version of PUT request 2022-01-09 21:45:48 +01:00
README.md Added README 2022-01-09 08:06:20 +01:00

README.md

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 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.