Linux

Where Does bCNC Store Config?

bCNC keeps user diffs in a home dot-file with system defaults beside installs. History and macros branch nearby.

Last updated

bCNC diffs user settings against install defaults in a home dot-file. Macros, workspaces and tool databases share the same INI with history beside. Upgrades overwrite system files only.

Project outputs land wherever saved with height maps beside G-code. Debug logs opt in per serial port with no default path. Copy user files while leaving system trees alone.

Where bCNC stores this, by platform

Linux
~/.bCNC

User diffs with macros, workspaces and tool DBs inside plus history beside. System defaults live apart and refresh on upgrade. Copy user side while closed.

Frequently asked questions

How do I back up bCNC settings?

Copy ~/.bCNC with history beside it while the app is closed. Diffs carry user settings against system defaults that upgrades overwrite. Macros, workspaces and tool DBs live inside the same file.

User versus system bCNC config?

They pair per role with user diffs overriding install defaults. Never edit system files directly since upgrades replace them. History tracks beside config with debug logs opt-in.

Where are bCNC project files?

They save wherever chosen with height maps beside G-code outputs. No fixed project home exists for this app. User buttons and workspaces stay in config regardless.

Notice an outdated path? Let us know.