When a user is created in the Nebari Slurm deployment, they have the following fundamental directories setup for them automatically (Separately they also have access to read-only software environment folders that are managed through an environment manager called conda-store):
/home/ - unique for every user
/shared - common for every user
Feature description:
Every user’s home directory will be made private such that they are only accessible to the user who owns it.
Value and/or benefit
At this point, every user in the Nebari Slurm has read-only access to every other user’s home directories. This is not ideal for most cases, imagine a situation when users are able to see every other user's home directories.
Feature description
Private Home Directories
Problem
When a user is created in the Nebari Slurm deployment, they have the following fundamental directories setup for them automatically (Separately they also have access to read-only software environment folders that are managed through an environment manager called conda-store):
Feature description:
Every user’s home directory will be made private such that they are only accessible to the user who owns it.
Value and/or benefit
At this point, every user in the Nebari Slurm has read-only access to every other user’s home directories. This is not ideal for most cases, imagine a situation when users are able to see every other user's home directories.
Anything else?
No response