this post was submitted on 20 Oct 2023
3 points (100.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

Hey all,

I am hosting applications on my home network via a raspberry pi in docker containers and I do not want to expose them over the internet. I’m trying to figure out how to configure my home network so that I can route requests going to “api.pi” to my web API running on my RaspberryPi and route “application.pi” to my web application. I’m not familiar with how home network and host names work, so looking for some guidance on how to get this setup.

you are viewing a single comment's thread
view the rest of the comments
[–] IVOreosFromHeaven@alien.top 1 points 1 year ago (2 children)

You’ll want a reverse proxy if you have multiple applications running on one Pi. You will also want a wildcard DNS entry pointing to the Pi for when you have the reverse proxy working

[–] Winux12@alien.top 1 points 1 year ago (1 children)

Yup, that makes since. I feel like since I have pi.local resolving to my raspberry pi on my home network then all I need to do is setup a reverse proxy with nginx or something that maps requests to my API or to my web application. What do you think? Or am I missing a step?

[–] IVOreosFromHeaven@alien.top 1 points 1 year ago

No yeah that’s all you need! NGINX I’d recommend for sure