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!
389 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 1156e896f7 Merge pull request 'cron: filter out repos with wrong architecture' (#163) from Chewing_Bever/vieter:cron-check-arch into dev 
Reviewed-on: vieter/vieter#163
 		2022-05-06 09:00:53 +02:00
.woodpecker ci(arch): also change URL of downloaded PKGBUILD 2022-05-05 23:38:12 +02:00
docs doc: listed new config variables in docs 2022-05-03 20:13:28 +02:00
src cron: filter out repos with wrong architecture 2022-05-06 08:31:59 +02:00
.dockerignore
…
.editorconfig
…
.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
CHANGELOG.md doc: added docstrings to all db/git functions 2022-05-03 20:02:05 +02:00
Dockerfile feat: simplified config down to pkg_dir & data_dir 2022-05-03 19:50:14 +02:00
LICENSE
…
Makefile docs: migrated over Hugo documentation 2022-05-01 12:14:13 +02:00
PKGBUILD ci(arch): changed PKGBUILD to new URL 2022-05-05 23:29:08 +02:00
README.md
…
renovate.json
…
test.py
…
vieter.toml feat: simplified config down to pkg_dir & data_dir 2022-05-03 19:50:14 +02:00

README.md

Vieter

Documentation

I host documentation for Vieter over at https://rustybever.be/docs/vieter/. API documentation for the current codebase can be found at https://rustybever.be/api-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!