The envy data/config filesystem /data is exposed as /admin to all users right now. This is intended to only be mounted for admin users. Right now, all users are "admin" users.
How it should work
With a fresh filesystem, any Github user can log in and the first one will be made admin. This user can then add users that are allowed to log in, and add which users are admins.
Imagining something stupid simple for both: /data/config/users and /data/config/admins. Both are just files with line separated usernames. When users file is not present, any user is allowed to login. When admin file is not present, first user to login is made admin and is written to admin AND user file.
On another note, perhaps the envy mount should be /admin to be consistent with environment mounted /admin, and we call it the "admin root".
progrium
commented
9 years ago
The envy data/config filesystem
/datais exposed as/adminto all users right now. This is intended to only be mounted for admin users. Right now, all users are "admin" users.How it should work
With a fresh filesystem, any Github user can log in and the first one will be made admin. This user can then add users that are allowed to log in, and add which users are admins.
Imagining something stupid simple for both:
/data/config/usersand/data/config/admins. Both are just files with line separated usernames. When users file is not present, any user is allowed to login. When admin file is not present, first user to login is made admin and is written to admin AND user file.On another note, perhaps the envy mount should be
/adminto be consistent with environment mounted/admin, and we call it the "admin root".