[CT] - Draft proposal for change in permission handling and user mapping #1144

Closed
opened 2025-03-14 08:27:55 +01:00 by muppeth · 7 comments
Owner

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:

  • Create a test env
  • Draft proposal
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: - [x] Create a test env - [x] Draft proposal
muppeth added the
sysadmin
housekeeping
labels 2025-03-14 08:27:55 +01:00
muppeth added this to the Currently working on milestone 2025-03-14 11:34:07 +01:00
Author
Owner

Drafted proposal (on cryptpad). @Disroot/Owners you're free to have a look and give feedback: sysadmin/Draft.....

Drafted proposal (on cryptpad). @Disroot/Owners you're free to have a look and give feedback: `sysadmin/Draft.....`
muppeth added the
🦾 5
label 2025-03-14 14:35:48 +01:00
Owner

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)

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)
Author
Owner

Answered the question and removed previous version of the draft.

Answered the question and removed previous version of the draft.
Author
Owner

Commands and the implementation is what will follow. this is just the general description of the problem and possible solution.

Commands and the implementation is what will follow. this is just the general description of the problem and possible solution.
Author
Owner

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.

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.
Owner

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.

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.
Author
Owner

Yup. I will try to document as much as possible and automate things too so it's easy to follow and implment elewhere.

Yup. I will try to document as much as possible and automate things too so it's easy to follow and implment elewhere.
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#1144
No description provided.