@@ -458,7 +458,7 @@ previously exported configurations. This is useful for:
458458
459459# ## Export a server configuration
460460
461- To export a running server's configuration to a file, use the
461+ To export a running server's configuration to a file, use the
462462[`thv export`](../reference/cli/thv_export.md) command :
463463
464464` ` ` bash
@@ -472,8 +472,9 @@ thv export fetch ./fetch-config.json
472472` ` `
473473
474474This creates a JSON file containing all the server's configuration, including :
475+
475476- Container image and version
476- - Environment variables and secrets
477+ - Environment variables and secrets references
477478- Volume mounts and permissions
478479- Network settings
479480- Transport configuration
@@ -493,18 +494,22 @@ For example, to run a server using the exported configuration:
493494thv run --from-config ./fetch-config.json
494495` ` `
495496
496- This creates a new server instance with identical settings to the original.
497+ This creates a new server instance with identical settings to the original. If
498+ the original server used secrets, you must have the same secrets available in
499+ your ToolHive secrets store.
497500
498501:::info
499- When running from a configuration file, you can still override specific
500- settings using command-line flags. For example :
502+
503+ When running from a configuration file, you can still override specific settings
504+ using command-line flags. For example :
501505
502506` ` ` bash
503507thv run --from-config ./fetch-config.json --name custom-fetch --proxy-port 8080
504508` ` `
505509
506510This runs the server with the exported configuration but uses a custom name and
507511port.
512+
508513:: :
509514
510515# # Next steps
0 commit comments