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
Consider how difficult it would be to have something listening to the hosts for either ssh or docker (or any other future providers) to ensure that when changes happen (to the containers being ran, or the underlying ssh config, etc) they are "immediately" reflected in netman. I don' t know what this looks like yet.
The text was updated successfully, but these errors were encountered:
Additionally we should consider how hard it would be to allow netman to manage its own provider hosts. This should be possible with the introduction of provider specific configurations (#135).
Configuration source is here and we are already creating configurations for consumers (such as Neo-tree). There is also some framework already in place to begin allowing providers to have their own configurations (require("netman.api").internal.get_config exists already, its just internal and thus not meant to be "exposed" yet).
Consider how difficult it would be to have something listening to the hosts for either ssh or docker (or any other future providers) to ensure that when changes happen (to the containers being ran, or the underlying ssh config, etc) they are "immediately" reflected in netman. I don' t know what this looks like yet.
The text was updated successfully, but these errors were encountered: