[bookbrainz-site] 14MonkeyDo merged pull request #1194 (03master…admin-panel-user-link): chore(admin-panel): Link to user with /user/name or /editor/id https://github.com/metabrainz/bookbrainz-site/pul…
yes makes sense, also if you have any feedback about changes you would like in the dashboard. happy to make those.
2025-11-21 32512, 2025
lucifer[m]
julian45: did anything change about the matrix installation recently? i think atj had a setting somewhere to make the ip of the postgres container static and hardcoded it in the systemd nspawn container running irc app service.
2025-11-21 32513, 2025
lucifer[m]
BrainzBot: ping
2025-11-21 32513, 2025
lucifer[m]
BrainzBot: ping
2025-11-21 32513, 2025
BrainzBot
Are you in need of my services, lucifer[m]?
2025-11-21 32513, 2025
BrainzBot
Are you in need of my services, lucifer[m]?
2025-11-21 32515, 2025
lucifer[m] sent a code block: https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/hiwAccuDnQQWIKWvgSbOCofY
2025-11-21 32517, 2025
aerozol[m] joined the channel
2025-11-21 32517, 2025
aerozol[m]
Fair enough! I feel I have to critical feedback or I'm not doing my job, but with that hat off the dashboard looks amazing 😍
2025-11-21 32517, 2025
aerozol[m]
So all good
2025-11-21 32517, 2025
aerozol[m]
Tbh I don't think we should waste valuable time making backend stuff (that looks and works good) visual changes for the sake of it
2025-11-21 32518, 2025
aerozol[m]
(Oh I should also say that I haven't done a comprehensive check/test of the functionality, just a quick look at everything before heading off on a trip this morning)
2025-11-21 32532, 2025
adhawkins_ joined the channel
2025-11-21 32556, 2025
lucifer[m]
IRC bridge back up.
2025-11-21 32514, 2025
lucifer[m]
julian45: let me know how you would like to document the steps for maintaining the irc bridge. i think atj wrote a doc but currently i cannot find it. also, how you would like to setup the repo for applying changes from upstream repo to our fork.
2025-11-21 32526, 2025
nawcom has quit
2025-11-21 32528, 2025
julian45[m] joined the channel
2025-11-21 32528, 2025
julian45[m]
yes, i think so - something about the docker engine's way of handling networks changed in a recent update and the settings in the MDAD host vars file were preventing matrix services from successfully starting. i commented them out and was able to get things to start.
2025-11-21 32541, 2025
julian45[m]
* vars file for pinning particular container IPs were preventing
2025-11-21 32511, 2025
julian45[m]
<lucifer[m]> "julian45: let me know how you..." <- for maintaining the bridge, syswiki is ok with me at this time if that works for you.
2025-11-21 32511, 2025
julian45[m]
for getting upstream changes into our fork, what i've done recently is simply navigate to a local copy of our fork on the same branch our production copy uses, set upstream as a new origin, and then did a git pull off that origin. this has git make me do a merge commit which then brings in all the changes from upstream at that time
2025-11-21 32513, 2025
lucifer[m]
Because of ipv6 or some specific restricted ports Ident needs to listen on the docker container was unusable and a systemd container was needed.d
2025-11-21 32538, 2025
lucifer[m]
julian45[m]: It does but the ipv6 Ident service. didn't work afair.
2025-11-21 32544, 2025
julian45[m]
why did/does the bridge need the same postgres as the synapse server, afayct? if that needed to be hardcoded against, i would have thought that would have been handled internally by MDAD (or been given its own separate container)
2025-11-21 32505, 2025
lucifer[m]
not familiar with irc bridge code but we don't have any custom modifications to it.
atp are you aware of any customizations that are actually specific to our fork and need to be maintained as a fork? (i.e. things that aren't just covered by gitignore on the upstream repo)
we're actually on the "discord" branch on the server itself iirc
2025-11-21 32544, 2025
lucifer[m]
hmm i see.
2025-11-21 32503, 2025
lucifer[m]
i think we should update to the latest master available upstream both deployment and our fork,
2025-11-21 32523, 2025
lucifer[m]
get rid of the extra branches, just keep master and production for now to remove confusion.
2025-11-21 32543, 2025
lucifer[m]
later on look into upstreaming changes if possible and avoiding the fork completely.
2025-11-21 32511, 2025
julian45[m]
lucifer[m]: this is the part i'm trying to clarify, and i'm sorry if you've already said it and i've missed something earlier (am on my phone so e.g. i didn't look at the compare link you sent):
2025-11-21 32511, 2025
julian45[m]
what changes needed for our use are currently justifying a fork?
2025-11-21 32509, 2025
lucifer[m]
discord bridge self building is the only change to the deployment code files.
2025-11-21 32545, 2025
lucifer[m]
rest all of the changes are in configuration files committed to the repo.
and just for my edification, what is the current need for self building? e.g., are we currently on an architecture for which the existing container option does not build?
2025-11-21 32556, 2025
wargreen has quit
2025-11-21 32508, 2025
wargreen joined the channel
2025-11-21 32548, 2025
lucifer[m]
acc. to my understanding yes. the VM is arm64. and iirc the MDAD requires self building for all architectures except amd64.
"For other architectures (e.g. arm32, arm64), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building).
2025-11-21 32530, 2025
julian45[m]
To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
2025-11-21 32539, 2025
julian45[m]
so if taken at its word, that implies that with as-is upstream, the playbook would simply detect there's no arm64 container for discord and handle building itself, no?
anyway for now, i'll try to reconcile our fork with the latest changes from MDAD. and we can look into upgrading the matrix bridge and the config etc. next week.
