Follow-up to #2.
Make the database connection configurable so HomeMemory can connect to an
existing Firebird 3.0 Server instead of the embedded engine. Each MCP
process still runs locally over stdio; only the database backend changes.
Embedded mode keeps the database next to the MCP process, so multiple
machines can't share it cleanly and shared file access hits lock issues.
Server mode removes both limits.
Connect-only: the server-side database must already exist, provisioned out
of band (file copy or gbak backup→restore). HomeMemory does not bootstrap
an empty server database.
Configuration via env vars:
HOME_MEMORY_DB_MODE = Embedded (default) | ServerHOME_MEMORY_DB_HOST, HOME_MEMORY_DB_PORTHOME_MEMORY_DB_PATH (server-side path or alias in Server mode)HOME_MEMORY_DB_USER, HOME_MEMORY_DB_PASSWORD (required in Server mode)
Embedded mode is unchanged.
Status
Code is implemented. Manual Firebird Server smoke test and setup
documentation are still pending.
Follow-up to #2.
Make the database connection configurable so HomeMemory can connect to an
existing Firebird 3.0 Server instead of the embedded engine. Each MCP
process still runs locally over stdio; only the database backend changes.
Embedded mode keeps the database next to the MCP process, so multiple
machines can't share it cleanly and shared file access hits lock issues.
Server mode removes both limits.
Connect-only: the server-side database must already exist, provisioned out
of band (file copy or
gbakbackup→restore). HomeMemory does not bootstrapan empty server database.
Configuration via env vars:
HOME_MEMORY_DB_MODE=Embedded(default) |ServerHOME_MEMORY_DB_HOST,HOME_MEMORY_DB_PORTHOME_MEMORY_DB_PATH(server-side path or alias in Server mode)HOME_MEMORY_DB_USER,HOME_MEMORY_DB_PASSWORD(required in Server mode)Embedded mode is unchanged.
Status
Code is implemented. Manual Firebird Server smoke test and setup
documentation are still pending.