Selfhosted

54792 readers

379 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Self hosting piefed (piefed.social)

submitted 5 days ago by a_person@piefed.social to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

Hello all,
I am attempting to self host piefed on a vps server running Debian 13 in docker with nginx proxy manager. I am at the step where I build it from source, and whenever I do it I get a ton of permission denied errors. I know the instructions said to chown 1000 the previous step, which I did but it still doesnt work. Thanks for the help.

you are viewing a single comment's thread
view the rest of the comments

[–] a_person@piefed.social 1 points 5 days ago (1 children)

Sorry, chown not chmod. And yes, in this section.

BUILD PIEFED

export DOCKER_BUILDKIT=1 sudo docker compose up --build

Wait until text in terminal stops scrolling. Ignore the configuration check errors at this point.
If you see many permission-related errors, try repeating the previous step **(with the chown command using 1000 instead of your username)**
Test external access from browser (On port 8030). Watch for movement in terminal window. Browser will show "Internal Server Error" message. Proceed to initialize database to address this error message.

[–] rimu@piefed.social 2 points 5 days ago

Ah ok.

That docker-dirs.sh script is trying to set the right permissions onto these directories:

"pgdata", "media", "logs", "tmp".

The owner of those directories needs to be the same user as the one running docker.