ci/woodpecker/tag/lint Pipeline was successful Details
ci/woodpecker/tag/docs Pipeline was successful Details
ci/woodpecker/tag/arch-rel Pipeline was successful Details
ci/woodpecker/tag/build Pipeline was successful Details
ci/woodpecker/tag/gitea Pipeline was successful Details
ci/woodpecker/tag/test Pipeline was successful Details
ci/woodpecker/tag/man Pipeline was successful Details
ci/woodpecker/tag/docker Pipeline was successful Details
ci/woodpecker/push/lint Pipeline was successful Details
ci/woodpecker/push/arch Pipeline was successful Details
ci/woodpecker/push/build Pipeline was successful Details
ci/woodpecker/push/test Pipeline was successful Details
ci/woodpecker/push/man Pipeline was successful Details
ci/woodpecker/push/docker Pipeline was successful Details
ci/woodpecker/push/deploy Pipeline was successful Details
ci/woodpecker/push/docs Pipeline failed Details
For more information, questions or just a chat, there's #vieter:rustybever.be on Matrix!
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.
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. Sadly, this didn't quite turn out the way I expected, but I'm sticking with it anyways ;p
- 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
Besides a V installer, Vieter also requires the following libraries to work:
Vieter also depends on some external V modules which you can install using
cd src && v install. Make sure to keep these dependencies up to date using
V is developed using a specific compiler commit that is usually updated whenever a new version is released. Information on this can be found in the tools repository.
If you wish to contribute to the project, please take note of the following:
- Rebase instead of merging whenever possible, e.g. when updating your branch with the dev branch.
- Please follow the Conventional Commits style for your commit messages.
docs directory contains a Hugo site consisting of all user &
docs/api on the other hand is a
Slate project describing the HTTP web
To modify the Hugo documentation, you'll need to install Hugo. Afterwards, you
can use the following commands inside the
# Build the documentation
# Host an auto-refreshing web server with the documentation. Important to note
# is that the files will be at `http://localhost:1313/docs/vieter` instead of
# just `http://localhost:1313/`
For the Slate docs, I personally just start a docker container:
docker run \
-p 4567:4567 \
--name slate \
-v $(pwd)/docs/api/source:/srv/slate/source slatedocs/slate serve
This will make the Slate docs available at http://localhost:4567. Sadly, this server doesn't auto-refresh, so you'll have to manually refresh your browser every time you make a change.