Files
memos/docs/design
boojack 83920cb3fb chore(cmd): warn at startup about unread /etc/secrets configuration
files

26.10.0 stopped reading the v0.31 deployment configuration files
(memos-idp-*.json, memos-instance-setting-*.json) without a migration,
so an
instance that kept them through the upgrade gave no sign of it beyond
the
settings that had silently reverted. Startup now logs one warning naming
any
such files still present under /etc/secrets, without reading them, and
points
at the configuration directory.
2026-11-01 21:35:34 +08:00
..

Design Documents

A design document records a decision and the reasoning behind it. Source code, tests, and package README.md or doc.go files describe current behavior; a design document does not have to.

Lifecycle

  • Draft. A design that is not yet shipped in a tagged release may change freely, even after its code is merged. Keep it in step with the implementation until the release, because the design itself often changes while a feature settles.
  • Implemented. Once the feature ships in a release, set Status: Implemented and freeze the body. Do not edit it to track later code changes.
  • Amendments. When a later release changes a frozen design, add or extend a dated ## Amendments section at the end that states what changed and why. Leave the original body intact, so the original rationale stays readable. A change large enough to need its own rationale gets a new design document that links back to the one it replaces.

Index

Implemented and frozen: