Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
Hi blondini — great question. SparkBox uses module-based compose files rather than a single master file. Each app has its own compose file under /opt/sparkbox/modules/. For adding a custom app, you have two main approaches: Option 1: Compose overrides — the cleanest way. Create a file at /opt/sparkbox/state/overrides/<yourapp.yml with your compose config. This persists across updates and is backed up with your other settings. Option 2: Portainer — access Portainer (available in your Apps) to manage containers directly through the UI. This gives you a GUI for adding and managing services. Which direction interests you? If you share what app you're trying to add, I can give you more specific guidance on the setup.
Chris wrote:
Perfect - Whisparr works great as a compose override. Create a file at /opt/sparkbox/state/overrides/whisparr.yml with this content: version: '3.7' services: sb-whisparr: image: lscr.io/linuxserver/whisparr:latest containername: sb-whisparr environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC volumes: - ${SBDATADIR}/whisparr/config:/config - ${MEDIAROOT}:/media ports: - "6969:6969" networks: - sbproxy restart: unless-stopped networks: sbproxy: external: true Then run sudo sparkbox up to create the container. Whisparr will be at http://BOX-IP:6969 on your LAN. The override persists across updates and is included in your backups. Let me know if you hit any issues.