About a year ago I built a website called #wvlist at https://wvlist.williamrehwinkel.net. But now I feel bad, because I built a custom web server but if I were to do it over I would just work on a customized #mediawiki page.
WVlist

Note that my #wvlist instance will be moving to https://wvlist.williamrehwinkel.net

I decided to let the wvlist.net domain go to cut down on cloud computing costs.
WVlist

wvlist

Werke Verzeichnis database with community submissions

Codeberg.org
Version 1.3.1 of #wvlist has had it's first release candidate made available. This fixes a bug in which the edit submit form would not work at all, due to an oversight while switching from hard-coded jquery URI to one that can be configured by the webmaster. This was alleviated and confirmed by headless chrome testing. I'm currently working on achieving a greater test coverage at the moment, for the next month before college starts. If all goes well, the full release for this patch will be made with no other changes in the next day.

https://codeberg.org/FiskFan1999/wvlist/releases/tag/v1.3.1-rc1
wvlist

Werke Verzeichnis database with community submissions

Codeberg.org
Once #wvlist is reworked to work from a single binary that embeds some files and accesses others in a different directory instead of the home directory of the repository, that will be available on my tap as well. For now, it is necessary to git clone and then compile from source.
The first release candidate of #wvlist v1.3.0 has been released. This update includes some updates to the password TUI and some opt-in changes to replicate behavior for the ever looming future major update. You can read about changelog here: https://codeberg.org/FiskFan1999/wvlist/releases/tag/v1.3.0-rc1
wvlist

Werke Verzeichnis database with community submissions

Codeberg.org
Released #wvlist patch update v1.2.2 today with a few changes, based on things i found in other projects, such as using strings.Fields instead of strings.Split
#wvlist update: Working on a PR which will change the behavior of #lilypond incipits in the next major update, but will be opt-in in the next minor update. With this change, wvlist daemon will disable internal caching of incipits, assuming that the administrator will use the better crafted caching of virtual hosting like #nginx. Follow along with the PR here: https://codeberg.org/FiskFan1999/wvlist/pulls/5/files #codeberg
lilypond RET renders incipit every time and doesn't save

I've coded in the behavior that will be the norm for the next major update, and will add it in the next minor update on an "opt-in" basis (previous behavior will stay for now). In this PR, the wvlist daemon will render each incipit on each request instead of the current behavior where it stores the png and serves that. Just put this together in the last few hours with a bit of copy paste, will need more testing.

Codeberg.org
#wvlist update: v1.2.0 first release candidate is up and running, I added an API endpoint to run administrator commands so that I can run a script to do admin tasks instead of logging in to the browser.
So I finally figured out a real reason to use nginx reverse proxies for my golang http applications…now I can listen on both host names “wvlist.net” and “www.wvlist.net” and use seperate certs for each. When I rework my personal blog WilliamRehwinkel.net to be completely statically hosted instead of using a runtime go daemon, I’ll probably move that over to the #wvlist vps, and then I’ll probably decide to disable my discord bot and be able to reduce cloud computing costs.