skadden

@skadden@ctrlaltelite.xyz

• ⁨Comment⁩ on ⁨Nextcloud alternatives⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  For what it’s worth you can convert the database to postgres if you want. I tried it out a few weeks ago and went flawlessly.

  docs.nextcloud.com/server/…/db_conversion.html

• ⁨Comment⁩ on ⁨Mullvad and Tailscale Announce Partnership⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Yeah I’ve been using it for about a year and half or so on my main devices and it’s been wonderful. I’m likely going to down the list of supported providers from the gluetun docs and decide from there. Throwing my torrents and all that behind a vpn was the catalyst for signing up so I’ll continue to look for that support first and everything else is secondary.

• ⁨Comment⁩ on ⁨Mullvad and Tailscale Announce Partnership⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’m pretty sure it’s entirely disabled. Their announcement post says it’s being removed and doesn’t call out any exceptions.

  I run my clients through a gluetun container with forwarding set up and ever since their announced end of support date (July I think?) I have had 0B uploaded for any of my trackers.

• ⁨Comment⁩ on ⁨Mullvad and Tailscale Announce Partnership⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Wow this is great. I’ve been having trouble getting exit nodes working properly with these two. Sad that mullvad dropped port forwarding though so I’m not sure if I’ll stay with them.

• ⁨Comment⁩ on ⁨"Support" containers - centralized or separate per service?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I do a separate container for each service that requires a db. It’s pretty baked into my backup strategy at this point where the script I wrote references environment variables for dumps in a way that I don’t have to update it for every new service I deploy.

  If the container name has -dbm on the end it’s MySQL, -dbp is postgres, and -dbs would be SQLite if it needed its own containers. The suffix triggers the appropriate backup command that pulls the user, password, and db name from environment variables in the container.

  I’m not too concerned about system overhead, but I’m debating doing a single container for each db type just to do it, but I also like not having a single point of failure for all my services (I even run different VMs to keep stable services from being impacted by me testing random stuff out.)

• ⁨Comment⁩ on ⁨Problem with updating Nextcloud on TrueNAS⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  It took a little bit of work but I rolled my own docker compose and it’s been pretty solid. I pin the specific nextcloud version in my compose file (I don’t like using :latest for things) and updating is as simple as incrementing the version, pulling the new image, and restarting the container. I’ve been running this way for a couple years now and I couldn’t be happier with it.

• ⁨Comment⁩ on ⁨How do you manage your Docker-compose or Podman data?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I host forgejo internally and use that to sync changes. .env and data directories are in .gitignore (they get backed up via a separate process)

  All the files are part of my docker group so anyone in it can read everything. Restarting services is handled by systemd unit files (so sudo systemctl stop/start/restart) any user that needs to manipulate containers would have the appropriate sudo access.

  It’s only me they does all this though, I set it up this way for funsies.

• ⁨Comment⁩ on ⁨that self hosted itch....⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’ve been running it behind Cloudflare with no issues. I’m also doing it a completely different way than the official docs and the ubergeek method. Mostly because I have a particular way I do my docker stuff.

  Every time something has broken it’s been 100% on me. My favorite way to learn is by breaking things though, so I also have an account on a different instance in case I break mine and have to wait a bit to fix it 😅

• ⁨Comment⁩ on ⁨that self hosted itch....⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  As someone else already said, automated backups should be up on the priority list.

  But also maybe try out self hosting Lemmy. It’s been a fun little journey and helped me flesh out my Caddy config more than I thought possible.

• ⁨Comment⁩ on ⁨Docker container reappears constantly after "rm" or "rm -f"⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Like others have asked, how exactly did you create these containers? If they were through Portainer did you use a compose file in a stack or did you use the GUI the entire way?

  This will nuke them assuming you don’t have something recreating them.

  docker ps -a # find your rogue container, copy the container id, my example is a0ff66a83c73
  docker stop a0ff66a83c73
  docker rm a0ff66a83c73
  

  My suggestion is to go through the process you did to try to deploy them and clean it up from that direction.

• ⁨Comment⁩ on ⁨hosting open multimedia library safely⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Are these people you trust? I would do Jellyfin and expose it to them via tailscale. Might be annoying for them to have to run tailscale but no chance I’m serving media directly from my house.