Technology

33586 readers

203 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

[email protected]

-1

Need advice regarding setting up network on LAN with Raspberry Pi (lemmygrad.ml)

submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]

0 comments fedilink hide all child comments

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?

no comments (yet)

sorted by: hot top controversial new old

there doesn't seem to be anything here