this post was submitted on 20 Aug 2025
28 points (88.9% liked)

Selfhosted

52596 readers
446 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 have a bunch of plain text recipe files on a NAS. If a family member wants to cook something, they ask me to print them a copy.

I’m looking for a simple as possible way to put them on a local web server via a Docker image or similar.

Basically all I need is to have http://recipes.local/ show the list of files, then you can click one to view and or print it.

Don’t want logins. Don’t need ability to edit files. Want something read-only I can set and forget while I continue to manage the content directly on the NAS.

What would you suggest?

you are viewing a single comment's thread
view the rest of the comments
[–] abimelechbeutelbilch@fulda.social 1 points 2 months ago (1 children)
[–] cute_noker 1 points 2 months ago (2 children)

Looks interesting, but also more complicated.

@cute_noker Maybe "oversized"; but https and password secured (for named users) 🔒

[–] abimelechbeutelbilch@fulda.social 1 points 2 months ago* (last edited 2 months ago) (1 children)

@cute_noker If you are familiar with #docker you can use #copyparty as simple as this:

docker pull copyparty/im && docker stop copyparty_photos && docker rm copyparty_photos

docker run -d -p 12345:12345 --name copyparty_photos \
--restart unless-stopped \
-v /path/to/photos/:/w \
-v /root/.config/copyparty:/cfg \
copyparty/im \
--https-only -nih -p 12345 \
--localtime \
--nos-hdd \
--grid \
--theme=6 \
-v /w::r,guest:rd,admin \
-a guest:pw1234 \
-a admin:anotherpw5678 \
--ipu=1.2.3.4/32=admin

TL;DR:
Path/to/photos = where your files are stored
-p 12345:12345 = Port to expose
Use https only!
User guest with PW can read
User admin with PW can read and delete
Autologin as admin if coming from IP 1.2.3.4

All parameters: https://ocv.me/copyparty/helptext.html

[–] cute_noker 1 points 2 months ago (1 children)

Looks very cool, seems like a good way to get started.

But it is hard to beat the simplicity of python.

The Dockerfile should work with this:

FROM python:3.13-slim WORKDIR /app COPY . /app EXPOSE 8000 CMD ["python", "-m", "http.server"]

[–] abimelechbeutelbilch@fulda.social 1 points 2 months ago (1 children)

@cute_noker #python wins by simplicity and a very small footprint. But it loses by security (if this is a matter for the data made available for the whole internet).

[–] cute_noker 2 points 2 months ago

Totally agree.