

I’m not an expert, but I think we need more information.


I’m not an expert, but I think we need more information.


Yes, good for me. Good for everybody. Yippee!


I’ve never needed to manually create a start menu entry. I install everything through the default repository or as a flatpak using the default software manager. I did have to manually enable flatpaks in the software manager (point for OP, admittedly).
Everything I’ve ever installed, including AppImages from time to time, always gets a start menu entry.


I use apps on my phone, but have no clue how to troubleshoot them. I have programs on my computer that I hardly know how to use, let alone know the inner workings of. How is running things in Docker any different? Why put down people who have an interest in running things themselves?
I know you’re just trying to answer the above question of “why do it the hard way”, but it struck me as a little condescending. Sorry if I’m reading too much into it!
To access things outside of your LAN (for example from your phone while at the grocery store), each service gets a DuckDNS entry. “service.myduckdns.com” or whatever.
Your phone will look for service.myduckdns.com on port 443, because you’ll have https:// certificates and that all happens on port 443.
When that request eventually gets to your router and is trying to penetrate your firewall, you’ll need 443 open and forwarded to your Debian machine.
So yes, you have it right.
Also forward port 80.
That question is a little bit out of the scope of a forum like this. A question like that would better be answered by the nginx documentation. Sometimes the project documentation might have a blurb about nginx configuration specific for that project. For example, Immich.
For the most part, you only have to reference the nginx documentation. I’ve never looked at the Immich config above until now, and my Immich server works great.
I’ve had a reverse proxy for years, but the config files are very foreign to me because I use Nginx-Proxy-Manager. NPM makes nginx usable for dummies like me, at the expense of gaining a deeper understanding of how it works. I’m ok with that, but you might feel differently.
For remote access, wireguard is great. You can access stuff via their internal addresses.


One of the few podcasts I listen to sometimes. Wishing them well and thanks for all of the hard work.
I’m a fan of Dockge. Nice simplicity, easy to update container stacks, etc. etc.


It looks like the hEX refresh is the same price from that vendor.
RB5009 is better but more expensive. There’s a PoE version that can power your WiFi APs in the future.
I also question the decision to put OpenWrt on it. RouterOS is solid. There’s a learning curve, but it’s worth it if you’re a nerd.


A while back, the docker installation instructions just had “lemmy:latest” as which version to pull. The Lemmy devs aren’t the brightest, and the beta versions are included as “latest”. Now the instructions have you put the specific version to pull, like “0.19.10”.
I wonder if that’s what happened?


From the GUI go to Datacenter - Notifications. Add a Notification Target of the Webhook type. Mine looks like this:

See the ntfy documentation for different types of authorization, tags (emojis), etc.
Then edit the default Notification Matcher and enable your new target.
By default I get notifications of successful/failed backup jobs. I want to set something up for drive health using SMART, but I’m just sitting down to figure that out now.


Ah, I responded above thinking you already had ntfy set up. Ntfy is so cool, I definitely recommend taking a look at it. I use it for notifications from Home Assistant, Uptime Kuma, Proxmox, etc. There are other similar things out there like Gotify, but I seem to prefer ntfy.


I think if you’re nerdy enough to self host stuff, you can definitely figure out LubeLogger. You don’t have to use all aspects of it… you can just use it for tracking gas mileage if you want.
If you want it to keep track of maintenance like oil changes and stuff, you have to add them manually and tell it how often you want them done.
For tracking gas mileage and maintenance reminders, all you need are 3 tabs - Service Records, Fuel, and Reminders. You can ignore everything else.


I responded to someone below. Hope it helps.


Since there’s no native ntfy notification built in to LubeLogger I figured out a way to do it using Node-RED. If you don’t have Node-RED set up, It’s pretty great for automating things. I mostly use it for Home Assistant. There’s certainly a way to accomplish this without Node-RED, but I would have no clue where to start.
The basic idea of the flow attached below is:
You’ll of course have to go through and change settings in each node to match your LubeLogger URL and vehicle ID’s, and preferred ntfy server and topic. You can also add your username/password for LubeLogger and ntfy (or a bearer token, if that’s what you have set up with ntfy).
If you’re not familiar with Node-RED, you’d import the above JSON and edit it from there. Stuff “flows” through nodes, stopping and doing what you tell it along the way.


I love LubeLogger. I’ve totally switched both my and my wifes cars to it for tracking gas mileage and maintenance.
If anyone would like, I can share how I got ntfy notifications working with it for maintenance reminders.


Good news, they just released v1.130.1


I used Portainer for a while and still like it for checking out networking stuff, but try out Dockge! It’s more open sourcey and basic, but makes updating easier.
I like the OnlyOffice software. It’s almost too good, like I feel like I should be wary of it. It has connections to Russia, but apparently it’s open source and all that jazz so from what I I understand it’s just good software.
Please correct me if I’m wrong.