this post was submitted on 01 Aug 2023
23 points (100.0% liked)

Selfhosted

40198 readers
518 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 noticed this trying to self host a teddit instance before the third party api thing happened and teddit still worked, i just didn’t think to post it until now. Is this normal?

you are viewing a single comment's thread
view the rest of the comments
[–] ayaya@lemdro.id 9 points 1 year ago* (last edited 1 year ago)

In the future if it is something you are really worried about it is normal to have subdomains for each docker container using something like nginx proxy manager. It is really easy to setup and you can have cookies for teddit.example.com and radarr.example.com separately.