Say how the spawned tools are actually invoked
This commit is contained in:
@@ -63,6 +63,22 @@
|
||||
// "unfiled":[…]}
|
||||
// import: one line per folder written, then a count
|
||||
//
|
||||
// RUNTIME MODES
|
||||
// mirror_folders.php --export
|
||||
// Print this host's folder layout as JSON, for the owner to compute a plan from.
|
||||
//
|
||||
// mirror_folders.php --import
|
||||
// Read a layout on stdin and apply it to this host's folder.view3.
|
||||
//
|
||||
// mirror_folders.php --containers=<csv>
|
||||
// Restrict the operation to these container names.
|
||||
//
|
||||
// mirror_folders.php --fallback-only=<csv>
|
||||
// Place only these into the partner's fallback folder, leaving the rest where they are.
|
||||
//
|
||||
// --dry-run
|
||||
// Compute and report the plan without writing folder.view3. Combines with any of the above.
|
||||
//
|
||||
// DEPENDS ON
|
||||
// /boot/config/plugins/folder.view3/docker.json the third-party layout, optional on import
|
||||
// SCRIPTS_DIR/docker_folders.json Varaverk's own layout — what the card reads
|
||||
|
||||
Reference in New Issue
Block a user