i think the old bootstrap path should stay documented

i think bootstrap mode still deserves a place in the docs, even if it is legacy. i tried moving a few smaller instances straight to the newer flow and ended up needing bootstrap references anyway to understand what the app was doing during first run.

version-wise, the behavior I saw was on a current release, and the confusion was not about the feature working. it was about knowing which settings were part of the old path and which ones were safe to ignore. i used the admin panel, the install docs, and a couple of log checks before I was comfortable. the answer was not to remove the old material. the answer was to mark it clearly and keep the migration notes beside it.

anyone else still relying on it for cleanup or recovery work?

Tagged:

Comments

  • Agreed. The legacy label helps, but removal would make troubleshooting harder when you inherit an older deployment.

  • I keep a copy of the bootstrap notes for exactly that reason. It has saved me during recovery more than once.