BlueForge Docs

forge sync

Sync fleet configs — hosting, storage, DNS, etc.

Command

forge sync <type> [--dry-run]

Arguments

NameTypeRequiredNotes
type
stringyesConfig type to sync (e.g.
hosting
,
storage
)

Flags

FlagTypeDefaultNotes
--dry-run
bool
false
Show what would change without applying

Examples

Sync hosting configs:

forge sync hosting

Dry-run:

forge sync storage --dry-run

Errors

Exit codeMeaning
0Sync completed successfully
1Sync failed

Pitfalls

  • Dry-run recommended — always use
    --dry-run
    first to preview changes before applying.
  • Destructive — syncing may overwrite remote configs.

See also

{auto-injected}

Tested against

{auto-injected}