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
sambacc provides a "setup steps" feature for some commands (mainly run) in which you can pass to have sambacc perform and explict set of setup steps before launching the main command (starting a long running process like smbd,winbind).
An example from a recent task did: run --setup=config --setup=users --setup=users_passdb --setup=nsswitch smbd
While it's nice that the setups steps are granular enough to provide a fine level of control over how sambacc sets up the environment its a bit to remember and type.
This was not a problem when samba-container images are mostly getting run via a higher level of orchestration like the samba-operator. However, when working in a low-orchestration environment this can be annoying
This is is a "I'm not commited to this, but let's think about it" to consider some sort of higher level way to invoke the setup steps - probably through the config file.
The text was updated successfully, but these errors were encountered:
sambacc provides a "setup steps" feature for some commands (mainly
run
) in which you can pass to have sambacc perform and explict set of setup steps before launching the main command (starting a long running process like smbd,winbind).An example from a recent task did:
run --setup=config --setup=users --setup=users_passdb --setup=nsswitch smbd
While it's nice that the setups steps are granular enough to provide a fine level of control over how sambacc sets up the environment its a bit to remember and type.
This was not a problem when samba-container images are mostly getting run via a higher level of orchestration like the samba-operator. However, when working in a low-orchestration environment this can be annoying
This is is a "I'm not commited to this, but let's think about it" to consider some sort of higher level way to invoke the setup steps - probably through the config file.
The text was updated successfully, but these errors were encountered: