[CT] - Draft proposal for change in permission handling and user mapping #1144
Labels
No labels
🔥
🦾 1
🦾 2
🦾 3
🦾 4
🦾 5
🦾 6
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
🙌 Decission needed
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
Goal 2025
help wanted
high impact
housekeeping
Howto
infra
In progress
🤔️ Investigate
Invoice Ninja
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low impact
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
PR ready
question
Ready
refined
Roundcube
searX
SPAM Issues
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Website
windows
wontfix
xmpp
Yearly Report
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#1144
Loading…
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?
To better handle the container data shares as well as improve user mapping inside containers providing more granular separation, we should first test and draft the proposal for implementation:
Drafted proposal (on cryptpad). @Disroot/Owners you're free to have a look and give feedback:
sysadmin/Draft.....
I've read it. A bit technical for me, but very interesting :) I added two comments.
Would also be nice to describe how this is done (commands for example)
Answered the question and removed previous version of the draft.
Commands and the implementation is what will follow. this is just the general description of the problem and possible solution.
I think the draft is ok to at least start with preping test env. There is quite some work I am planning to do on my homelab setup which is going to be a great test case for the production implementation as some of the things could be applied back to prod, including the matter of this project.
Don't forget to update documentation if needed when implementing stuff on your setup and to let me know what you do, so that I can have a setup that looks similar to what you have.
But yeah, the draft is fine, I got the overall idea.
Yup. I will try to document as much as possible and automate things too so it's easy to follow and implment elewhere.