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
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
ACL-based permission management is complicated doesn't work well. I had an idea today for a simple "just make the damn thing world-readable" system that would be based on chmod and file watching.
Because we would repeatedly chmod -R o+rwX folders, it's better if we limit the number of files it targets, so we'll ask users to indicate which subfolders, in their shared folder, should be world-writable. Something like:
Considering that shared folders are mostly only used in development environments, I'm guessing that making some folders world readable isn't much of a problem. We would, of course, clearly indicate the "world readable" aspect of the thing in the docs.
The process would go something like this:
On lxdock up, run chmod -Rf o+rwX on all writable paths, on the host.
On lxdock halt, do the same, but on the guest.
Add a new lxdock sync command that would behave like vagrant rsync-auto (possibly using entr?). It would chmod on both the host and the guest.
ACL-based permission management is complicated doesn't work well. I had an idea today for a simple "just make the damn thing world-readable" system that would be based on
chmod
and file watching.Because we would repeatedly
chmod -R o+rwX
folders, it's better if we limit the number of files it targets, so we'll ask users to indicate which subfolders, in their shared folder, should be world-writable. Something like:Considering that shared folders are mostly only used in development environments, I'm guessing that making some folders world readable isn't much of a problem. We would, of course, clearly indicate the "world readable" aspect of the thing in the docs.
The process would go something like this:
lxdock up
, runchmod -Rf o+rwX
on all writable paths, on the host.lxdock halt
, do the same, but on the guest.lxdock sync
command that would behave like vagrant rsync-auto (possibly using entr?). It wouldchmod
on both the host and the guest.This would replace the ACL system.
Closely related to #46. Ping @robvdl .
The text was updated successfully, but these errors were encountered: