Neither have sauce in them, they are more akin to a calzone

Is it just me or does that “comparison” make no sense for this thread. It’s mostly comparing vaultwarden to the cloud version of bitwarden, not the self hosted version. It only mentions the self hosted version in passing. It doesn’t do anything to help someone choose between vaultwarden and self hosted bitwarden

I’m not sure if I would even recommend starting with fdm if your goal is resin. So little that you learn about fdm actually transfers to resin, they really are that different. If your end goal is resin because you want to make miniatures, you’re just wasting money getting an fdm printer.

It sounds like what you need to do at this point is find what IP address your lemmy instance and mastodon instance containers are using on your VPS. you can do “docker inspect containername” and look for the IP address in there. it might be something like 172.16.0.1 for lemmy and 172.17.0.1 for mastodon. then you want to set up your reverse proxy to point lmy.my-domain.tld to 172.16.0.1:80 (or whatever port you set lemmy to use) and then mstdn.my-domain.tld to point to 172.17.0.1:80 (again, port might be different, i dont know what the default port is)

-IF- both of the containers are using the same IP, then you will need to make sure that they are using different ports. if they are on the same ip and same port, whichever container loads 2nd will fail to properly load, because when a port is taken on an IP address, it is reserved and nothing else can try to listen on that port.

So a reverse proxy is sort of like a phonebook or directory, it routes outside requests to the appropriate place. So imagine your reverse proxy is a receptionist, someone comes in and says “hey I am looking for plex.mydomain.com” the receptionist would then use the phonebook and say “ok if you are looking for plex.mydomain.com, go to building 192.168.1.10 (the ip), room 9000 (the port)”

Since you are asking about dockerized services, the networking for those can be done in several different ways, but the one thing that really matters is that each service needs to have a unique combination of ip and port, because only 1 service can live at each address. With docker, you could set up multiple services that use the host server’s ip, in which case each container will need to be on different ports, or you could have it so each container has its own ip, in which case the port can be anything.

homeassistant community store has a cloudflared add-on that works great to get it to easily work over cloudflare tunnels

Just fyi how a client handles multiple DNS servers might not always be you expect and just depends on how it was implemented. Some clients can just send a DNS request to all DNS servers at once and take whatever responds first, essentially randomizing which DNS server gets used

I’m not gonna lie, between the dirty camera lens and the color of the filament, I can’t tell wtf is going on in this pic at all

Yeah, I think it falls squarely into your thing about a new term from open source as its not recognized as being open source by the OSI and probably won’t be due to it being too restrictive, but the restrictions close the loopholes, forcing the software to be more free at the same time so it’s kind of in a weird spot

MongoDB has a modified version of the AGPL that they call Server Side Public License that might interest you. Specifically the change in section 13:

“Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.

By my reading, it closes that loophole you mention by specifically calling out interfaces and APIs as also requiring the source to be available. At the top of the page I linked there is also a PDF showing the removals and additions they made to the AGPL to end up with their SSPL.

I’m fairly certain hardware based 2fa has been around since the early 90s maybe even earlier. It’s not the maturity that’s the issue, as I’m fairly certain its significantly older than application based, but that it’s extremely inconvenient for the user to have to buy a physical key and keep it safe

Think about what happens to water if it’s heated above 100C… it turns into steam! The more water there is in the plastic the more steam there will be, causing the various issues like bubbling. The release of steam also means some of the heat is not being absorbed by the filament, leading to temperature issues as it exits the nozzle

I would also test by connecting to the vpn and trying to go to a service’s ip or ping an ip on the network behind the vpn from the browser. I use juice and ovpn on my router as well and it works fine, so its unlikely to be a juice specific problem

I had a similar issue where it was thin in regular intervals similar to what it looks like in your pics, the issue I had was the extruder gear was clogged up on one side so it wasn’t gripping the filament and slipping until it spun around to the unclogged side and it would extrude normally again.

Typically you’d have a server running on a device on each UPS, and the clients would be the other devices also plugged into that UPS, so when that UPS is low, everything plugged into it will turn off. If you have another UPS elsewhere in the house, you would have another server installed on a device there so it can monitor that UPS that it is plugged into, and tell the other devices also plugged into that other UPS to shut down. Without knowing the layout you are running though, there’s no way to know if NUT is what you need or want.

So in your case it would likely be to plug your server and nas both into the same UPS, and when the server detects the UPS is low battery, it will tell the NAS to shut down. This would also require the switches/router/whatever to also be on a UPS to hold power of course. So then it basically becomes each little cluster of devices that need UPS would also have a switch nearby that is also on the UPS

Look into NUT, Network UPS Tools. It runs in a server/client type of set up. You’d install the server onto the device that has the UPS data connected to it. It then monitors the UPS status and can tell all the clients to shutdown when the UPS is running low.