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
Mode 1 runs a command on the container but affects the host computer's configuration files.
Mode 2 a workspace is created and only the container's configuration files are affected.
Mode 1
Is it really safe to modify configuration files on the host computer when the command runs from the container OS?
The host computer files would be in the format from the container. So mixing c3tk and local host could be dangerous.
Should there be container wrapper scripts that do things implicitly to the host computer's configuration files?
(Example installing plugins that the host computer did not have installed already)
Mode 2
Does it make sense to have wrapper scripts when using workspaces versus and explicit initialization?
If something fails in the wrapper, that failure is repeated all the time.
The text was updated successfully, but these errors were encountered:
There are two modes to running c3tk commands.
Mode 1 runs a command on the container but affects the host computer's configuration files.
Mode 2 a workspace is created and only the container's configuration files are affected.
Mode 1
The host computer files would be in the format from the container. So mixing c3tk and local host could be dangerous.
(Example installing plugins that the host computer did not have installed already)
Mode 2
If something fails in the wrapper, that failure is repeated all the time.
The text was updated successfully, but these errors were encountered: