You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent incident we needed to modify a file in a user's home directory, but the file was preventing hub sessions to start. We weren't sure how to modify the file without spawning a user's session.
We realized that this was possible via exec-homes-shell which is documented in the deployer module.
We should have a section in infrastructure/ that is called something like ## How to access and modify a user's filesystem. This is where our documentation about exec-homes-shell should live, and the "move a hub" docs should reference this section. This would make the information more glanceable and discoverable.
Updates and actions
No response
The text was updated successfully, but these errors were encountered:
Context
In a recent incident we needed to modify a file in a user's home directory, but the file was preventing hub sessions to start. We weren't sure how to modify the file without spawning a user's session.
We realized that this was possible via
exec-homes-shell
which is documented in the deployer module.This is documented in
infrastructure/
as part of deleting a hub, but not in the context of accessing / modifying a user's filesystem.Proposal
We should have a section in
infrastructure/
that is called something like## How to access and modify a user's filesystem
. This is where our documentation aboutexec-homes-shell
should live, and the "move a hub" docs should reference this section. This would make the information more glanceable and discoverable.Updates and actions
No response
The text was updated successfully, but these errors were encountered: