When config.toml already has a database_url, setup prefills it, so a blank answer keeps the existing URL and there is no way to select the bundled socket database (and generate PGPASSWORD) short of typing its URL. Done when a re-run offers the bundled database as an explicit choice.
Imported from beads archie-core-ittv · GitHub #1570 · type bug · priority P2 · created 2026-10-05
When config.toml already has a database_url, setup prefills it, so a blank answer keeps the existing URL and there is no way to select the bundled socket database (and generate PGPASSWORD) short of typing its URL. Done when a re-run offers the bundled database as an explicit choice.
---
_Imported from beads `archie-core-ittv` · GitHub #1570 · type bug · priority P2 · created 2026-10-05_
Already fixed by ebc6dd67e: a setup re-run offers the bundled database as an explicit choice (internal/infrastructure/configuration/setup/setup.go:156).
Already fixed by ebc6dd67e: a setup re-run offers the bundled database as an explicit choice (internal/infrastructure/configuration/setup/setup.go:156).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When config.toml already has a database_url, setup prefills it, so a blank answer keeps the existing URL and there is no way to select the bundled socket database (and generate PGPASSWORD) short of typing its URL. Done when a re-run offers the bundled database as an explicit choice.
Imported from beads
archie-core-ittv· GitHub #1570 · type bug · priority P2 · created 2026-10-05Already fixed by
ebc6dd67e: a setup re-run offers the bundled database as an explicit choice (internal/infrastructure/configuration/setup/setup.go:156).