

And terrible at adminning
And terrible at adminning
They can’t get back into Reddit, they’re just gone
It takes all of 30s to spin up a new Reddit account, just has to have a new name that isn’t already taken. If anything it’s easier than on a lot of Lemmy instances
after like the 3rd time I was forced stop it from hiding my library and them pushing services in my face
Seeing shit like this makes me wonder what different Plex I’m using from everyone else. Pinned my local library at the top 4 years ago and now every device shows that tab first when logging in and hasn’t ever behaved differently except when the home server is down (it’ll still go to the tab but read OFFLINE)
Don’t post identifying shit in the first place if you don’t want it up. Learn how search functions work if you don’t wanna manually shift through shit.
Like I said: loss of information because people are whiny babies about this shit is a bigger deal to me than someone removing information nobody else actually gives a shit about
No, I’m not. As stated: reading comprehension
My problem is mass deletion without consideration. Obviously if something is identifiable: remove it, but don’t do so en masse without looking. It’s not ideal, but it’s your right to remove identifying info. If it doesn’t actually ID someone they should leave it the fuck alone
Great reading comprehension dude
Honestly? No, they should t be able to blanket delete everything theyve posted on the off chance it’s identifiable information
They should have the right to find that info and remove it, but I’m 1000% against people potentially taking down useful information from society and I do not care that people want to whine about their “right” to take their fucking ball back and end the game
So much useful info gone from Reddit because babies didn’t want to keep supporting the bad site and now good luck finding it anywhere else
it keeps non tech savvy people out,
Picking a server isn’t a tech savvy person thing to do and it’s a good idea to stop pretending like it is. My wife, who needs me to move her steam games to other drives for her, managed to do it without asking me a thing. Tech skill has nothing to do with it
Must have, I still have a porn Tumblr that absolutely sees fresh content
The obvious solution to this is Lemmy devs noticing that this is a feature most/all apps use without active support and thus add support to Lemmy itself. Devs will naturally keep to icons that are similar to the default icons
It’s a legitimate thing to want and would be a great addition for sure
Been thinking about swapping away from Plex when I move to New hardware later this month
If I’m reading all this right sounds like Overseerr and Plex both can be replaced with this, as well as a unified app for the two?
If so I’m def getting this installed and testing it out this weekend, my goal for a while has been to get the rest of my family into my streaming ecosystem but having to use 2 whole apps (Plex and Overseerr on a website) is enough to scare them away despite using 6 apps currently
It took me too long to get everything working myself because people love to share shit exclusively in CLI format and look down at anyone who asks for YAML it seems, so I’m always glad to pass it on
(I can understand CLI, but the ADHD brain finds YAML much easier for documentation purposes and it surprises me how many people seem to disagree)
Ok, had my wife send me the file from my network
networks:
main-network:
name: ${COMPOSE_PROJECT_NAME}
attachable: true
ipam:
driver: default
config:
- subnet: configure
ip_range: this
gateway: yoself
services:
# Gluetun - <https://github.com/qdm12/gluetun>
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
networks:
- main-network
cap_add:
- NET_ADMIN
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=wireguard
- VPN_PORT_FORWARDING=true
- VPN_PORT_FORWARDING_PROVIDER=protonvpn
- WIREGUARD_ADDRESSES=use your own
- WIREGUARD_ALLOWED_IPS=0.0.0.0/0
- WIREGUARD_PRIVATE_KEY=nope
- WIREGUARD_PUBLIC_KEY=69420
- WIREGUARD_DNS=
- VPN_ENDPOINT_PORT=
- VPN_ENDPOINT_IP=
volumes:
- ${DOAPPDAT}/gluetun:/gluetun
I left in the wireguard stuff without my details because for me Gluetun refused to work when setting the exact same info to wg0.conf, so I define it in my compose
Then, services that rely on gluetun go below and look like:
# qBittorrent - <https://hub.docker.com/r/linuxserver/qbittorrent>
qbittorrent:
container_name: qbittorrent
network_mode: container:gluetun
image: lscr.io/linuxserver/qbittorrent:latest
depends_on:
gluetun:
condition: service_healthy
restart: unless-stopped
Works perfectly when I run it through portainer
What works for me:
Networks first in docker-compose
Gluetun first in Services, uses the network I set for it and the stack
Everything else goes below it, relying on the gluetun CONTAINER (I plan to have another stack running gluetun for other reasons so having it check the service is a no go for me) to be running in a HEALTHY state
All are set to restart: unless-stopped except gluetun, which is never
The expected behaviour is that containers will always wait for gluetun to report that it’s healthy before trying again to restart. Should gluetun fail and crash for any reason it won’t reboot and potentially fuck itself up harder, and no services will be able to start because it’s not reporting healthy.
This works perfectly in portainer and should when running docker-compose up, but for me it took portainer to work. Saw someone somewhere mention it has some sort of priority handling override built into it that docker itself doesn’t, meaning it’s less likely to fuck that lind of thing up, but idk how true it is
I’ll see if I can remember to snag a couple snips of my YAML to make it more clear
My main 2 reasons for installing it both come from needing to restart services sometimes:
Portainer let me allow other people access to restarting specific containers that occasionally misbehave
Portainer lets me update and restart all of the containers running in my VPN stack without breaking. For some ungodly reason, even with dependency set and everything in docker-compose, a CLI reboot will basically always start a service or 2 before gluetun is actually advertising it’s in a healthy state and everything breaks. With portainer that doesn’t happen, with the exact same compose, and I don’t get why lol
Ok i get it, it’s best practice to do rushed releases without QA because users are the free testers.
You literally used the wrong version. As I stated: the app you’re talking about clearly states it does not have a stable release for the version of nextcloud you’re running.
They definitely had no way to know that their own app was incompatible
They knew, and told you, right on the app page
Idiot user who believed their newsletter "update now, hub 9 is the best thing ever
You said it, not me. I tried being nice but that really is what happened: you fell for what the marketing team wrote and skipped basic IT steps in doing so. Now, rather than just admit you made a mistake that a LOT of people have made (including me, I’m a fucking idiot too) you are whining and doing your best to me talk gymnastics this into you being a victim of something
How you managed to convince your IT department of anything with a knowledge that shallow and an attitude like that I’ll never know. Grow up.
then a bit of warning is suggested
Which was given by the app that gets broken by the update
Windows doesn’t tell you that upgrading to 11 will break x, y, and z that you have installed, you’re expected to go to the sites for those programs and check if they work. Same exact idea
The same company making both apps is never a guarantee that they’ll play nice day 1, for many reasons
I’ll repeat: learn from your mistake instead of blaming other people for your naivete. If an app is important and might break during an update of something: check the apps documentation to see if it supports said update
Literally just googled “nextcloud forms” and looked at their supported versions and whaddya know, it says right on that webpage that there’s no stable version for 30 yet, so safe bet would be that it wouldn’t properly work when upgrading:
There is a supported nightly build, though, so you could probably have tried that
It’s on you to look up what will break when you update, or to test and see what happens when you do. A major update page isn’t going to list all of the things that rely on it that break because that’s fucking unreasonable
I’m starting to see a pattern in those comments like “why did you wear a skirt that night? It looks like you asked for it…”
Cute victim mentality, but gross and insanely wrong comparison
Learn from your mistake and don’t update without testing next time, it’s 100% on whoever updates the production environment to make sure that shit isn’t broken for whatever reason before pushing it customer-side
It’s more like you bought a random white powder from your dealer without asking what it was and are now upset you almost died
On a public forum?
Lol you wish