JakeBreath
2d9493d9fe
install.fish now: - asks for the API origin (default https://j621.rainbow-herring.ts.net) and an optional token when run interactively, or takes --url/--token; - writes ~/.config/j621Greeting/config.fish with mode 600 (it may hold a token), keeps an existing config unless --force/--url is given, and --no-prompt runs fully unattended; - verifies the setup: /health must answer 'ok' and a fastfetch random roll is attempted, reporting the API's own message when it finds nothing; exits non-zero when the backend is unreachable so scripts notice. README documents the prompts/flags, the chmod 600 config, and that the greeting is designed to run without a token (guest mode: unsigned links, guest-visible items only) with a token adding signed links and hidden items. Tested with fish 4.9.3 in throwaway HOME dirs: flag-driven install with a token, interactive install with a piped origin and no token, re-run keeping the existing config, and an unreachable backend exiting 1.
fish_greeting (updated for the J621 rewrite)
Shows a random library image as your shell greeting, using fastfetch. This is
the updated version of the script from
J621-Django/extras/fish_greeting system/fish_greeting.fish, adapted to the
new REST API.
What changed from the old script
| Old J621-Django | This version | |
|---|---|---|
| Endpoint | GET /random/?rating=X returned image bytes |
GET /api/random/?fastfetch=1&rating=X returns JSON |
| Image access | same response, X-File-MD5/X-File-Name headers |
signed url from the JSON, downloaded separately |
| Unsupported types | rolled again (recursion) | server only returns png/jpg/gif in fastfetch mode |
| Config | hardcoded https://j621.jake.i |
J621_BASE / J621_TOKEN / J621_WEB |
| Printed link | /view/<md5> on the old host |
/detail/<J-ID> on J621_WEB |
| Modes, logging, gifsicle, fastfetch flags | same | same (~/.config/fish/greeting_mode, ~/.config/j621Logos/logs.log) |
The gm-switch helper and the .desktop launchers from the old repo keep
working unchanged: they write the same ~/.config/fish/greeting_mode file
(0 = NSFW, 1 = SFW, 2 = Questionable).
Install
cd extras/fish_greeting
fish install.fish
Then edit ~/.config/j621Greeting/config.fish (at least J621_BASE) and test:
fish_greeting
Requirements: curl (or wget), fastfetch, file. Optional: gifsicle
(GIF downscaling), jq or python3 (JSON parsing — without either it falls
back to grep/sed).
Configuration
Any of these work; the config file is read by the function on every run:
# ~/.config/j621Greeting/config.fish, or universal variables
set -g J621_BASE https://j621.rainbow-herring.ts.net # API origin
set -g J621_WEB https://j621.example.ts.net # link origin (split deploys)
set -g J621_TOKEN <api token> # signed URLs + hidden items
set -g J621_FASTFETCH_CONFIG jake # fastfetch config name
J621_TOKEN is the same token the SPA uses (Authorization: Token …). With
it the API signs the image URL for your account, so you also get items that
are hidden from guests. Without it the greeting runs as a guest and sees the
public library only.
Rating filters
greeting_mode |
Rating requested | Label |
|---|---|---|
0 |
e |
NSFW |
1 |
s |
SFW |
2 (default) |
q |
Questionable |
Troubleshooting
No logo (No image matches those filters.)— the library has no images for that rating; try another mode or add files.No logo (API error)— checkJ621_BASE, and that the deployment is up (https://<host>/health).No logo (download failed)— the signed URL expired (they last 24 h) or the item was deleted between the two requests; just run it again.- The greeting is slow — the API and image fetch have
--max-timeguards; a slow tailnet link is usually the cause.