🐞 Bug: Homebox ; extra environment variable needed for 0.26+ versions

Bug Description

After updating Homebox using docker compose pull && docker compose up -d, it stopped working.

Apparently, when going from 0.25 to 0.26+ (now it's at 0.26.2 when using the ghcr.io/sysadminsmedia/homebox:latest image URL), an environment variable HBOX_AUTH_API_KEY_PEPPER is expected.

So, I updated my .env to include it
`#version=1.0
#url=https://github.com/2Tiny2Scale/tailscale-docker-sidecar-configs
#COMPOSE_PROJECT_NAME= // only use in multiple deployments on the same infra

SERVICE=homebox
IMAGE_URL=ghcr.io/sysadminsmedia/homebox:latest
SERVICEPORT=7745

TS_AUTHKEY=****
DNS_SERVER=9.9.9.9

HBOX_LOG_LEVEL=info
HBOX_LOG_FORMAT=text
HBOX_WEB_MAX_UPLOAD_SIZE=10
HBOX_AUTH_API_KEY_PEPPER=some_random_string
`

I generated the random string with this command:
openssl rand -base64 48

And I put this line in my docker-compose.yaml:
- HBOX_AUTH_API_KEY_PEPPER=${HBOX_AUTH_API_KEY_PEPPER}

This allowed me to run the latest version of Homebox.

Please also note that the image URL used in your .env is no longer the active version of homebox.
this is now the active image url:
ghcr.io/sysadminsmedia/homebox:latest

Expected Behavior

to work

Actual Behavior

doesn't work without adapting .env and docker-compose.yaml

Screenshots

No response

Operating System

Linux

Tailscale Version

1.98.4

Docker Version

28.3.0

Relevant Logs or Error Messages

Docker Compose Configuration

Environment Configuration (.env file)

Additional Context

No response

Inspect the Homebox service settings in the repository's .env and docker-compose.yaml, then compare them with the reported 0.26+ requirements. Check that HBOX_AUTH_API_KEY_PEPPER is passed through and that the image uses ghcr.io/sysadminsmedia/homebox:latest. Run docker compose pull and docker compose up -d to verify the updated configuration starts successfully.