FAQ

Frequently asked questions about Nimbus.

Does Nimbus support two-way sync?

No. Nimbus is one-way: local data/ to a remote target. For two-way sync, run a separate process against a different bucket and diffMode: hash to avoid clobbering files.

Can I sync to more than one target?

Not from a single config. Run multiple workspaces, each with its own nimbus.config.json and target, and point --workspace at each in turn or in separate CI jobs.

How does Nimbus decide what changed?

By default it compares file modification times against the last successful sync. Set diffMode: hash to compare content hashes instead — slower, but correct when mtimes aren’t reliable (see Troubleshooting).

Is there a GUI?

No, Nimbus is CLI-only by design. nimbus watch --verbose is the closest thing to a live view.

Where are logs stored?

Nimbus logs to stdout/stderr only; it doesn’t write its own log files. Redirect output if you need persistence:

nimbus watch >> nimbus.log 2>&1