686 - Actualiza tus contenedores Docker SIN dolor. Dockge, Cup y Homepage
Actualiza tus contenedores #docker de otra forma utilizando #dockge#cup y #homepage de forma sencilla y con todo el control en tus propias manos
El último episodio, el 685, titulado Adios Portainer. Dockge lo destrona, trajo varios comentarios, y uno de ellos me llamó la atención, porque hablaba d
Actualiza tus contenedores Docker SIN dolor. Dockge, Cup y Homepage n Actualiza tus contenedores #docker de otra forma utilizando #dockge#cup y #homepage de forma sencilla y con todo el control en tus propias manos
#portainer ha sido el rey de la gestión de #docker via web en los últimos tiempos, pero hay otras opciones como por ejemplo #dockge que es mas sencillo
Como sabes soy un amante de la terminal, mas que nada por la productividad que me ofrece. De esta forma, prácticamente todo lo hago desde la termin
Adios Portainer. Dockge lo destrona n #portainer ha sido el rey de la gestión de #docker via web en los últimos tiempos, pero hay otras opciones como por ejemplo #dockge que es mas sencillo
Networking & Remote Access:#Tailscale (non-Docker), love its SSH agent and magic DNS features. #NetworkSecurity
Security & Monitoring
Ad Blocking:#AdGuardHome (non-Docker). Previously used PiHole but find AdGuardHome slightly faster. #PrivacyTools
Server Monitoring:#Beszel (non-Docker). Tried Grafana/Prometheus/Alertmanager (accessible but overkill) and Netdata (poor screen reader accessibility). Beszel isn't perfect but best compromise so far. #ServerMonitoring
RSS Feeds:#Miniflux (non-Docker), excellent accessibility. Originally wanted better podcast support but other options had major accessibility issues. #RSSReader
IRC Client:#TheLounge (non-Docker). Some accessibility issues but best I've found so far for always-connected IRC. #IRCClient
Read Later Service:#Wallabag (Docker). Biggest issue is Wallabagger Chrome extension doesn't work for me yet. #ReadItLater
Notifications & Development Workflow
Notifications via: #Ntfy (Docker) and Zoho's ZeptoMail (#Zoho)
Development Environment: Mostly using VSCode connected to my server via Remote-SSH extension. #VSCodeRemote
Accessibility Focus ️
Accessibility heavily influences my choices—I use a screen reader full-time (#ScreenReader), so I prioritize services usable without sight (#InclusiveDesign, #DigitalAccessibility). Always open to discussing accessibility experiences or recommendations!
Habit trackers like Beaver Habit Tracker (#HabitTracking): Accessibility issues made it unusable for me.
I don't really have a media collection, so no Plex or Jellyfin here (#MediaServer)—but I'm always open to suggestions! I've gotten a bit addicted to exploring new self-hosted services!
What's your setup like? Any cool services you'd recommend I try?
I tried to set up Docker and Dockge, then I tried to make a Jellyfin container. It didn’t go well at all. I couldn’t find any clear, working configuration examples for getting Jellyfin container to look at my external SSD for media files. I spent 12 hours yesterday on and off, looking at conflicting tutorials and smug how-tos and I’m done with Docker and associated external drive frustration. Docker whale, meet ocean.
I just straight up slapped Jellyfin on Ubuntu from the repository and launched it. It’s running now. I had to futz around with directory permissions to get it to access the external SSD. I learned a lot about chown and chmod, but mostly chown -R lol.
Ubuntu has so much conflicting information about its network system structure that I think I went more bald looking for how to set a static IP address for the server. Every time I set static, it would lose internet access. This is a 10 second job on Windows or macOS that took over an hour to iron out. My router config was fine, thanks. I limited the DHCP range and used an IP outside the range for the static address for the RPI. I got it sorted by accident, which Is frustrating because I don’t have a clue what the problem was.
I’ve used up a lot of computer spoons and I don’t want to look at it anymore today.
This morning, I started to check out #Dockge to replace my #Portainer and Portainer-Agent in my #homelab. This open-source project, created by the same developer as #UptimeKuma, looks very cool and beautiful.
Unfortunately, it is not yet for me; it's missing an important option to group stacks by their agent. I have containers running on multiple hosts like cAdvisor, Telegraf, and Watchtower. However, this feature is in progress; I will keep an eye on it
Just installed Dockge to manage my handful of Docker containers, and I am sad I didn't try it sooner!
Getting this running was ridiculously easy, and I was even able to have it manage my existing containers just by copying my compose files to a new location.
Plus I get a terminal view into the container AND I can see and modify my compose file!
I’ve just switched from #portainer to #dockge. I was tired of Portainer issues with my docker compose files. Dockage is much more transparent and easy to use and let you interact directly with your compose.yaml files #dev#docker
@Bradcopter#qbittorrent has experimental #i2p integration, if your setting up a stack. I recommend #dockge for breezy af container management and #gluetun for making sure all the traffic stays on i2p. Trash guides is a good place to start, it’s pretty comprehensive, if uh dryly written. You can get pretty granular control over the media that gets downloaded. I use mine with #Jellyfin as the frontend, you can even set it up jellyseerr to automate requests. Like having your own streaming service, you can run the whole thing on a pretty low end pc, mine is an old chrome box that I got on eBay for $20. For simplifying remote access and security, I run everything on Nebula mesh overlay.