This commit is contained in:
2026-09-18 14:11:10 -05:00
parent b3ceac52ed
commit 1170e6e9c1
2 changed files with 21 additions and 0 deletions
+1
View File
@@ -25,6 +25,7 @@ frontend/dist/
.vscode/ .vscode/
.idea/ .idea/
.DS_Store .DS_Store
.directory
# Tooling # Tooling
*.log *.log
+20
View File
@@ -34,6 +34,13 @@ the tools it needs and then verifies the backend: `/health` must answer and a
random roll is attempted. It exits non-zero when the backend cannot be random roll is attempted. It exits non-zero when the backend cannot be
reached. reached.
It also appends a guarded block to `~/.config/fish/config.fish` that sources
the function. That is needed on setups whose distro/theme config (CachyOS,
Oh My Fish, hand-rolled `config.fish`) defines `fish_greeting` inline while
the shell starts — such a definition wins over autoloading from
`functions/`, so ours has to be loaded afterwards. The block is written once
and repeated installs leave it alone; pass `--no-config` to skip it.
Non-interactive / re-install: Non-interactive / re-install:
```fish ```fish
@@ -89,6 +96,19 @@ guest and sees the public library only.
## Troubleshooting ## Troubleshooting
- **The distro/theme greeting still shows** (CachyOS, Oh My Fish, …): those
configs define `fish_greeting` while the shell starts, which beats
autoloading. Check what fish resolved:
`functions --details fish_greeting` — it must point at
`~/.config/fish/functions/fish_greeting.fish`. If it points at a distro
file, run `fish install.fish` again (it adds the source block to
`config.fish`) or add it yourself:
```fish
if test -f ~/.config/fish/functions/fish_greeting.fish
source ~/.config/fish/functions/fish_greeting.fish
end
```
at the **end** of `~/.config/fish/config.fish`.
- `No logo (No image matches those filters.)` — the library has no images for - `No logo (No image matches those filters.)` — the library has no images for
that rating; try another mode or add files. that rating; try another mode or add files.
- `No logo (API error)` — check `J621_BASE`, and that the deployment is up - `No logo (API error)` — check `J621_BASE`, and that the deployment is up