Skip to content

fix(stack): name instances installed before the installer wrote a name - #118

Merged
arthware-dev merged 1 commit into
mainfrom
fix/product-name
Sep 23, 2026
Merged

arthware-dev merged 1 commit into
mainfrom
fix/product-name

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

The installer only started writing [core] name on 2026-09-22. An instance installed earlier has none, so it calls itself "stack" and searches ~/stack-extensions for extension stacklets, while the docs and every fresh install use ~/famstack-extensions. An extension put where the docs say is not found.

The data dir has always been written as ~/<name>-data. When [core] name is missing and that dir exists, the next stack command writes the name into [core] and says so. Nothing is written for an instance with a name, without a data dir, or with a data dir not named <name>-data.

Fixes: d281407 ("feat(stack): load stacklets from extension directories")

The installer only started writing `[core] name` on 2026-09-22. An
instance installed earlier has none, so it calls itself "stack" and
searches `~/stack-extensions` for extension stacklets, while the docs
and every fresh install use `~/famstack-extensions`. An extension put
where the docs say is not found.

The data dir has always been written as `~/<name>-data`. When
`[core] name` is missing and that dir exists, the next `stack` command
writes the name into `[core]` and says so. Nothing is written for an
instance with a name, without a data dir, or with a data dir not
named `<name>-data`.

Fixes: d281407 ("feat(stack): load stacklets from extension directories")
@arthware-dev
arthware-dev merged commit e7c15c6 into main Sep 23, 2026
1 check passed
@arthware-dev
arthware-dev deleted the fix/product-name branch September 23, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant