test
/
vieter
forked from vieter-v/vieter
1
0
Fork 0
Code Issues Pull Requests Releases Activity
Archlinux repository server, written in V. For questions, info, or a chat, join #vieter:rustybever.be on Matrix!
347 Commits
5 Branches
3 Tags
1.7 MiB
V 90.7%
Python 5.2%
Makefile 2%
Dockerfile 1.4%
Shell 0.7%
 
 
 
 
 
Go to file
Jef Roosens 20707f6af1
chore(ci): change debug build used 
chore(ci): removed skip-unused-static experimental build

chore: updated Makefile
 		2022-04-30 11:58:49 +02:00
.woodpecker chore(ci): change debug build used 2022-04-30 11:58:49 +02:00
src Eh don't feel like writing scheduler rn 2022-04-14 21:20:10 +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 chore(ci): change debug build used 2022-04-30 11:58:49 +02:00
CHANGELOG.md Switched to official compiler instead of fork 2022-04-15 10:59:05 +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 chore(ci): change debug build used 2022-04-30 11:58:49 +02:00
PKGBUILD Switched to official compiler instead of fork 2022-04-15 10:59:05 +02:00
README.md Switched to official compiler instead of fork 2022-04-15 10:59:05 +02:00
renovate.json Add renovate.json 2022-04-11 10:01:38 +00:00
test.py Solved the "removing old packages" problem (I think) 2022-04-09 21:08:54 +02:00
vieter.toml Eh don't feel like writing scheduler rn 2022-04-14 21:20:10 +02:00

README.md

Vieter

Documentation

I host documentation for Vieter over at https://rustybever.be/docs/vieter/.

Overview

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.

Compiler

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.

Features

  • 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

Building

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!