It’s not mine. Feel free

On mobile so you’ll have to forgive format jank.

It depends how each image handles ports if C1 has the ports set up as 1234:100 and C2 has the ports set up as 1234:500 then:

service:

gluetun:

ports:

 - 1234:100 #c1
 - 1235:500 #c2

[…]

Will solve the conflict

Sometimes an image will allow you to edit it’s internal ports with an environment so

service:

gluetun:

ports:

  - 1234:1000 #c1
  -1235:1234 #c2

c1:

environent:

- UI_PORT=1000

[…]

When both contsiners use the same second number, C1: 1234:80, C21235:80, and neither documents suggest how to change that port, I personally haven’t found a way to resolve that conflict.

If they come in wool, sign me up. I’ve been pricing up a full set of wool socks and it’s eye-watering. I think I’m going to be asking for wool socks for Christmas/birthdays for a couple years … my mid-life transformation is complete.

A mini pc, a raspberry pi 4, 3*usb HDD (2*8tb mirrored and a 1tb for local back up), some Netgear router, a whole lot of spaghetti.

I’m obviously not going to make your argument for you.

Having it one sided clearly doesn’t defeat the purpose of votes. When you went to the ballot box do you upvote your chosen candidate and also downvote your least favourite?

Not having downvotes is a simple statement: “If you do not like this thing, we don’t care”. Report the spam and block the creators you don’t like, simples.

So you use my logic for upvotes, which you clearly didn’t, and maybe you’ll see why it’s downvotes that are removed and not upvotes.

See, if downvotes were active you might have just gainsayed and moved on and we wouldn’t have had this interaction. Neat huh?

That’s a shame. TTeck pretty much built my Homelab.

Not that I have a solution but engoraging people to use “blocks” and “filters” is the way to go I think.

I’d like to create a homepage but Lemmy moves too slowly for that, so I do find myself on “all” a lot. So blocking users/communities/instances and filtering keywords are how I craft a positive experience here.

When EH was around I’d waste endless time trolling/downvoting them, which I now realise was time wasted. It didn’t help me; made Lemmy more toxic; and gave bad actors the legitimacy and attention they want.

I think my comment in the poll was fairly comprehensive, so I’ll leave it at that. Except to add good job LemmyNSFW admins you constantly handle controversy well. From instance bans, instance drama or this current downvote issue, no notes.

You’re not a train. You don’t need to announce your departure.

I feel downvotes are fairly useless.

They’re used as a disagree button. Ok but why do you disagree? Leave a reply and let’s discuss. Gain saying has little value and that’s all a downvote to disagree is.

They’re used to report spam. Spam should be reported so I don’t think that’s a valid argument for them. Downvoting spam leaves it up, reporting spam gets it taken down. We have a better solution to spam than downvotes.

They are used by bad actors, with the removal of downvotes bad actors have to spend more effort in making a comment and it becomes far more obvious in who they are, report and block them.

Finally downvotes are a way to yuck someone’s yum, I’m mindful of the instance we’re on. I don’t want our communities to become like Reddit where only one genital configuration and body type are allowed.

My initial inception of this box was to have it request a static IP so I knew “box.ip”. Then tape then tape some thing like this:

Box.ip Service1:port Service2:port …

Onto the case. Then in NPM have it proxy requests to “box.ip:8096” to “tailscale.ip:8096”. But alas, I couldn’t figure it out. I could get 1 service to work but not multiple.

I couldn’t ask someone to write the config for me, but if you’re certain it’s doable then I’ll learn to write a config. Thank you for the offer. I’m guessing for each service I tell nginx to “listen” at “port” instead of only listening to ports 80,443 and 81.

MDNS seems like an interesting solution though, I’m going to read about that now actually, thank you for highlighting that solution to me. If I could get that working that would be ideal. I’ll have to check if the expected devices are compatible but that would make everyone’s life easier if I could just setup a cronjob on startup.

Thank you for the reading material, it’ll be tonight project. I think I’m just going to tell people if they want to join in the family immich/mealie/etc they’ll just have to let me into their router. They’ll get memorable addresses out of it and adblocking too. I’m pretty sure that setup is comfortably within my skill set. I thought long and hard about opening ports but the security needed is beyond me currently. Down side is cost and I’ll be managing a bunch of boxe. But I can add updating them into the monthly maintenance and if/when they come back they can be repurposed into other projects.

I tried /locations but my service would rewrite the URL and break itself. I’d navigate to “box.ip/immich” and immich would change the address to “box.ip/login” and hang.

I’d need to learn how to have npm lock “box.ip/immich” and let immich append “/login”. I’ll leave my test VM up and just chip away at it. I think I need the “rewrite” flag but I’m getting dangerously close to just learning how to write an nginx config instead of having npm do it for me.

Thanks again for the pointers

Yeah, that’s a fair description. I am not comfortable exposing ports currently, I don’t think I have the skill to do it securely and my Homelab is definately not secure enough.

Not to get side tracked, and to highlight the horror, my media library is chmod 777 until I figure permissions across LXCs.

Can you imagine my fiancée’s dissapointment when I showed her my “finger tricks”…

Oh, routing, I remember watching an “off site back up” video where they set up IP tables, or IP forwarding, or some such, so when their parents tried to access jellyfin locally it was routed over tailscale. Maybe I’m misremembering though, I’m not confident enough to start thinking about it seriously, so I logged it as “that’s possible” and moved on.

That way I just have to keep one instance of jellyfin/immich/etc up to date. It’s all a bit beyond my ken currently but it’s the way I’m trying to head. At least until I learn a better way.

Ideally, I give someone a pi all set up. They plug it in go to service.domain.xyz and it routes to me. Or even IP:Port would be fine, I’ll write them down and stick it to their fridge.

My parents and I run each others’ off-site back up (tailscale-syncthing), but their photo and media services are independent from mine. I just back up their important data, and they return the favour, but we can’t access or share anything.

Guides like yours are great for showing what’s possible. I often find myself not knowing what I don’t know so don’t really know where to start learning what I need to learn.

What a write up, thank you for documenting this.

I understand a lot of people in this hobby do it professionally too, so a lot is assumed to be common knowledge us outsiders just don’t have.

While my system of using tailscale’s magic dns to use lxc:port works fine for my fiancée and I, expanding this a family wide system would prove challenging.

So this guide is next step. I could send my fiancée to <home.domain.xyz> and it’ll take her to homarr, or <jellyseerr.domain.xyz>

The ultimate dream would be to give family members a pi zero and a <home.domain.xyz> and then run a family jellyfin/immich.

Someone identifying with Homelander would. That’s the real meme here.

I remember Watchtower helpfully stopping Pihole before pulling the new image when I only had the one instance running… All while I was out at work with the fiancée on her day off. So many teaching moments in so little time.

Home server: Proxmox (Debian). Redundant DNS: Raspbian (Debian). Parent’s server: Debian (Debian).

Gonna be honest, I mostly live off my phone and a retroid pocket.

Linux does what Windont?

I should probably keep sharing Linux Isos longer than I do, but data hording has a low WAF. Instead I have prowlarr set the ratio to 3 (one for me, one for a leecher, and one to add to the pool) to keep the data churning.