Archlinux repository server, written in V. For questions, info, or a chat, join on Matrix!
Go to file
test 24b0898a36 Update 'Makefile' 2022-05-05 09:23:25 +02:00
.woodpecker Update '.woodpecker/.arch.yml' 2022-05-05 09:19:10 +02:00
docs docs: migrated over Hugo documentation 2022-05-01 12:14:13 +02:00
src feat(cron): added debug log on build_repo failure 2022-05-02 07:50:44 +02:00
.dockerignore Switched to patch-based builder, based on weekly 2022-01-27 19:18:11 +01:00
.editorconfig Just some changes to poke CI 2022-03-27 23:33:33 +02:00
.gitignore docs: migrated over Hugo documentation 2022-05-01 12:14:13 +02:00
.gitmodules docs: migrated over Hugo documentation 2022-05-01 12:14:13 +02:00 Update '' 2022-05-05 09:18:41 +02:00
Dockerfile Renamed data_dir to repos_dir 2022-04-07 15:21:27 +02:00
LICENSE Added AGPLv3 license [CI SKIP] 2022-01-27 22:34:12 +01:00
Makefile Update 'Makefile' 2022-05-05 09:23:25 +02:00
PKGBUILD fix(ci): only download PKGBUILD instead of cloning entire repo 2022-04-30 22:22:12 +02:00 docs: added docs command & notice in README 2022-04-30 14:19:08 +02:00
renovate.json Add renovate.json 2022-04-11 10:01:38 +00:00 Solved the "removing old packages" problem (I think) 2022-04-09 21:08:54 +02:00
vieter.toml feat(cron): added removal of old builder images 2022-04-30 18:38:24 +02:00



I host documentation for Vieter over at API documentation for the current codebase can be found at


Vieter is a restart of the Pieter project. The goal is to create a simple, lightweight self-hostable Arch repository server, paired with a system that periodically builds & publishes select Arch packages. This would allow me to build AUR packages (or PKGBUILDs I created myself) "in the cloud" & 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.


Vieter compiles with the standard Vlang compiler. However, I do maintain a mirror. This is to ensure my CI does not break without reason, as I control when & how frequently the mirror is updated to reflect the official repository.


  • Arch repository server
    • Support for multiple repositories & multiple architectures
    • Endpoints for publishing new packages
    • API for managing repositories to build
  • Build system
    • Periodic rebuilding of packages
    • Prevent unnecessary rebuilds


In order to build Vieter, you'll need a couple of libraries:

  • An installation of V
  • gc
  • libarchive
  • openssl

NOTE: if you encounter any issues compiling Vieter using the absolute latest version of V, it might be because my mirror is missing a specific commit that causes issues. For this reason, the make v command exists which will clone my compiler in the v directory & build it. Afterwards, you can use this compiler with make by prepending all make commands with V_PATH=v/v. If you do encounter this issue, please let me know so I can update my mirror & the codebase to fix it!