Fix first-run check: gbrain writes config under $GBRAIN_HOME/.gbrain/ #3

Merged

Jriyuu merged 1 commit from fix/entrypoint-gbrain-home-check into main

2026-10-02 09:38:20 +10:00

Gideon commented

2026-10-02 08:53:35 +10:00

Member

The container idled forever after gbrain init: the first-run check looked for $GBRAIN_HOME/config.json, but gbrain treats GBRAIN_HOME like a home dir and writes its config under $GBRAIN_HOME/.gbrain/. Now treats the container as initialised if EITHER path exists.

Caught during the gideon-pi deploy. Verified with bash -n.

The container idled forever after `gbrain init`: the first-run check looked for `$GBRAIN_HOME/config.json`, but gbrain treats GBRAIN_HOME like a home dir and writes its config under `$GBRAIN_HOME/.gbrain/`. Now treats the container as initialised if EITHER path exists. Caught during the gideon-pi deploy. Verified with `bash -n`.

Gideon added 1 commit

2026-10-02 08:53:35 +10:00

Fix first-run check: gbrain writes config under $GBRAIN_HOME/.gbrain/

Build and push Docker image / build-arm64 (pull_request) Successful in 56s

Details

Build and push Docker image / build-amd64 (pull_request) Successful in 1m0s

Details

Build and push Docker image / merge-manifest (pull_request) Has been skipped

Details

3056947f7f

gbrain treats GBRAIN_HOME like a home dir and writes its config at
$GBRAIN_HOME/.gbrain/config.json (not $GBRAIN_HOME/config.json). The old
check never saw a config after 'gbrain init', so the container idled
forever instead of serving. Now treats initialised if EITHER location
exists (works whether gbrain uses .gbrain/ or the bare dir).

Caught during the gideon-pi deploy.