this post was submitted on 18 Jul 2025
42 points (100.0% liked)

Selfhosted

49672 readers
591 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 2 years ago
MODERATORS
 

I've been working on a Threadiverse frontend for almost a year called Blorp. Originally it was Lemmy only, but now it also includes PieFed. (source code) (try web version)

I just Dockerized the frontend and started publishing the Docker image, and I would love your feedback!

  • REACT_APP_DEFAULT_INSTANCE (e.g. https: //lemmy.zip no trailing slash)
    • Changes the default instance
  • REACT_APP_LOCK_TO_DEFAULT_INSTANCE set this to "true" or "false"
    • When true, this prevents the frontend from logging into other instances. Perfect if you host your own Lemmy instance and want this frontend to exclusively be used with your instance. You can still log into multiple accounts on the locked instance
    • When false, you can log into as many accounts across as many instances as you want. You can even mix and mach Lemmy and PieFed
# pull the latest Blorp image
docker pull christianjuth/blorp:latest

# run it on port 8080 (host → container), passing any runtime env‑vars you need
docker run -d \
  --name blorp \
  -p 8080:80 \
  -e REACT_APP_DEFAULT_INSTANCE="https://lemmy.zip/" \ # BUT without the trailing slash!
  -e REACT_APP_NAME="Blorp" \
  -e REACT_APP_LOCK_TO_DEFAULT_INSTANCE="false" \
  christianjuth/blorp:latest

Edit: I cannot get the trailing slash in https://lemmy.zip/ to go away, but make sure you exclude it. Idk what sorcery is going on with Lemmy, but it seems impossible to link a domain without a trailing slash. I'll make the docker image more forgiving in the next update.

you are viewing a single comment's thread
view the rest of the comments
[–] shnizmuffin@lemmy.inbutts.lol 4 points 3 days ago (1 children)

No, not at all.

They are a shorthand for "give me the index of this directory" rather than "give me the first file you find named this." In some configurations, the presence of absence of a trailing slash dramatically reduces the amount of computation an HTTP server must execute before responding to the request.

[–] moseschrute@lemmy.world 2 points 3 days ago

Unpkg.com shows different results based on trailing /