Dutch software engineer, supporter of N.E.C. !nec@ymmel.nl
That’s rough… No idea how I’d cope with that. I don’t think I’ve ever had a datacap on any residential connection here in the Netherlands. Currently got 1gbps fiber up and down for 50 euros I think.
TV however is still a huge scam. I just want to watch football but have to have a billion other channels too I think. (Ima see if I can change this now lol)
It’s the LSIO image hooked up to seperate (but also docker) postgres db that’s also used for other apps. The data and config directories are bind mounts to the local filesystem. It connects to a samba share via the external storage plugin. It is exposed to the internet through a caddy reverse proxy though (the database isn’t)
Not sure if I completely understand but I think you want public service 1 accessible on subdomains s1.domain.com and internal service 2 on s2.domain.com?
Just point the A record for s2 to an internal ip address (or a tailscale ip). The only thing dns does is translate a (sub)domain to an ip address. So outside of your network s2.domain.com wouldn’t resolve but inside your network it would.
How I understand it is that database/io calls are heavy and network calls are relatively light. A user on the instance itself equals Database/io and a federated server means just 1 database call and a bunch of network calls. Since it’s a push model the instance only has to retrieve the data from the database itself once and then just pushes it to all subscribed instances.
Yep started using https://hoppscotch.io it’s basically a clone
Just got to have a backup. I have children so for pictures anything Google is just not doable. Nextcloud on my home NAS, nightly backup to Amazon Glacier (super cheap to store because it’s expensive to retrieve) in case of a catastrophic failure (like fire). Every month or so backup the files to an external drive.
Uhh apparently posted on ur other thread https://ymmel.nl/comment/128500
Can you reach file browser regularly? Attach it to a bridge network and expose the correct port to see if the container is running properly. Or check the docker logs for it. Could be that the reverse proxying isn’t working but I’d check the actual container first and go from there.
Awesome will give this a try