

Don’t forget about linkwarden
Don’t forget about linkwarden
Just cross your fingers nobody attempts to import it…
Doesn’t avoiding JS typically structure a website in such a way that the browsers built-in assistive services can cover it easier?
It does inherently lean into the concept of corporate forks over community forks. A byproduct of prioritizing monetary gain. I think the license is really just a foot in the door to allow for community audits. Realistically I don’t see anyone wanting to contribute to something like this unless the product has slim to no real competition.
I’ve also witnessed matrix structure break down when too many methods of communication are used. It’s all very brittle.
Or it’s a cheap external nvme chassis with a Samsung 980 Pro. Had to run that when I was copying files from one of my old machines and boy, it will absolutely overheat to the point of failure.
Gave me quite the scare when I started getting read errors and then it dropped off the bus. It shutdown to protect itself but it certainly didn’t seem like that at the time.
Just note that if you somehow get out of those meetings, incorrect information will be propagated somehow. Even if you put the correct answers in an email and send it to everyone involved. If someone has a way to prevent that from happening please let me know. It’s killing me slowly.
I use the linuxserver images for Nextcloud. Have worked pretty well for me over the past few years.
Reformatting that compose for people:
version: "2.1" services:
wireguard:
image: linuxserver/wireguard
container_name: wireguard
cap_add:
- NET_ADMIN
- SYS_MODULE
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Singapore
- SERVERURL=auto #optional
- SERVERPORT=51820 #optional
- PEERS=1 #optional
- PEERDNS=auto #optional
- INTERNAL_SUBNET=10.13.13.0 #optional
volumes:
- ./config:/config
- /lib/modules:/lib/modules
ports:
- 51820:51820/udp
sysctls:
- net.ipv4.ip_forward=1
- net.ipv4.conf.all.src_valid_mark=1
restart: unless-stopped
Sounds like you didn’t read the extended manual: https://github.com/linuxserver/docker-wireguard
There are a lot of other configs for that container that must be provided before startup. It’s just a generic runner. If you want it to run as a server you need to follow this section: https://github.com/linuxserver/docker-wireguard?tab=readme-ov-file#server-mode
Are you at getting the handshake in the app? If so, you’re probably just missing the dispatch commands for traffic masquerading.
This is unrealistic, agile stages aren’t missing unusual pieces that aren’t quite critical but probably should be there anyway.