mirror of
https://github.com/go-shiori/shiori.git
synced 2026-04-25 22:45:55 +03:00
[PR #209] [CLOSED] Inherit user id/group for created directories and files #539
Labels
No labels
component:backend
component:builds
component:builds
component:extension
component:frontend
component:readability
database
database:mysql
database:postgres
database:sqlite
feature:ebooks
github_actions
good first issue
hacktoberfest
note:duplicate?
note:fixed?
note:out-of-scope?
os:windows
priority:high
priority:low
pull-request
resolution:as-intended
resolution:cant-reproduce
resolution:duplicate
resolution:fixed
resolution:wontfix
tag:TBD
tag:big-task
tag:help-wanted
tag:huge-data
tag:meta
tag:more-info
tag:next
tag:no-stale
tag:requires-migrations
tag:research
tag:security 🛡️
tag:stale
tag:waiting-for-assignee
type:bug
type:documentation
type:enhancement
type:meta
type:ux
user:cli
user:web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shiori#539
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/go-shiori/shiori/pull/209
Author: @rcribbs
Created: 10/28/2019
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
581f9d5Inherit user id/group for created directories and files.📊 Changes
2 files changed (+18 additions, -1 deletions)
View changed files
📝
internal/cmd/root.go(+6 -0)📝
internal/core/processing.go(+12 -1)📄 Description
I use shiori on my server in docker, but I prefer to lock down the shared mount to a user on the host server.
As it stands shiori just always creates everything under root so even if it's run under another user it doesn't play well in creating files/directories.
These changes are only in the core and in the initial data directory creation. I imagine there are some other parts of the code that could use this treatment for consistency as well, but I'm only using these portions so I only addressed these portions of the code.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.