• 3 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle








  • 1111@lemmy.worldOPtoLinux@lemmy.mlWindow snapping
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I’ve got this now, looks pretty cool, thanks! Gonna keep looking over the documentation, but I can’t quite see the particular behaviour I’m looking for. It has the snapping (and better options than Win10), but I want to be presented with the list of other available windows for snapping on the other side.



  • 1111@lemmy.worldOPtoSelfhosted@lemmy.worldNetworking Help
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Hi!

    The hostname thing is weird. I was able to navigate to the hostname in my browser which successfully showed the mediabox landing page (I believe this is ‘Homer’), but all the links on there were pointing to the machine IP. If I changed the address to be hostname:32400, maybe it would have worked, but I didn’t try that. I guess homer should route to a machine IP not a localhost so as when you land there from another device it properly routes to the machine which can serve the apps.

    Aside: Do you (or anyone reading!) know how you do that thing where you alias your machine IP to an arbitrary name? I’m sure I did it once upon a time with ‘bonjour’(?), but I don’t recall any more than that.

    Anyway, turning the deco’s onto access point mode solved everything :)

    Regarding mediabox - there seems to be a few good projects like this, they are actually incredible and super helpful for a learning perspective. I started with YAMS which actually has miles better documentation and is super helpful for setting up the services. Mediabox seems to assume you know a bit more about how the *arrs work. It sets up the containers and the folder structures really nicely, but for a novice like myself it took some time to get all the applications configured.

    It’s been a fun project though!


  • 1111@lemmy.worldOPtoSelfhosted@lemmy.worldNetworking Help
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Sure thing! I’ll answer everything as best I can.

    The machine is a single laptop running Mint. All the docker containers are being served from this machine, and during this testing I was trying to access them all from that same machine. I observed the containers were up and running properly with docker stats cmd and I saw they were accessible over the original IP when using the ISP WiFi.

    The access points are TP Link Deco, it’s 3 units, the first of which is connected via ethernet to my ISP provided router (Virgin Media Superhub). I believe they are WiFi meshing. I can’t tell too much more about how they work ‘under the hood’ as the setup was very… ‘consumer friendly’ and didn’t cover much technical detail

    When I connect to this network and run ifconfig it looks like the IP changes in the last few digits. I thought if I used that IP with appropriate ports I might be able to view my servers, but that was not the case.