this post was submitted on 22 Aug 2023
25 points (96.3% liked)

Selfhosted

40041 readers
703 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.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I'm reading up on self-hosting Lemmy, and I was planning on creating my own private instance for individual use on some spare Azure ASP I use to host private FreshRSS (not rich to host a public service).

This basically shuts my idea down, because I wanted to simply host my account myself and browse all of Lemmy as I please.

So is everyone hosting individual instances dealing with them being public? is there a workaround to avoid having a public service that anyone can see?

you are viewing a single comment's thread
view the rest of the comments
[–] poVoq@slrpnk.net 8 points 1 year ago

The federation/API end point and the web-ui are entirely independent.

If you want, you can run the federated backend with no web ui at all and use it via mobile apps only.

Or you could put some password protection via the webserver in front of the web ui only.