Title is a bit vague because I don’t know the correct terms to phrase it properly.

I have a Raspberry Pi that I use to run jellyfin, transmission, blocky, soju. Recently I added libreddit to it seeing how the rate limits are affecting public instances.

The problem is that currently if I need to go my libreddit instance, I have to go to 192.168.0.x:xxxx which is extremely unfun to type.

Is there a way I can access it more elegantly? One solution I found was to configure blocky with a custom DNS that points to the RPi where I can configure an nginx reverse proxy so that lr.rpi.local for example serves libreddit.

Any other ideas for this?

  • @[email protected]English
    2•1 year ago

    Not sure if this helps, as I’m not 100% certain how I set this up (it was too long ago), but by giving my rpi a hostname I can simply use ‘pizero.local’ from my desktop machine. I don’t run a DNS server per se but maybe look into that kind of dhcp / dns option?