Hi, I would like to add https://fireshare.net/ to my SparkBox. Is there a way i can do this, i'm guessing in Portainer, without breaking current setups? Thanks
5 replies
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:
Good news: that won't break your current setup, and Portainer is exactly the right tool — it's bundled with SparkBox. One thing to know up front: the App Store only contains SparkBox's curated apps, and there isn't a one-click "add any app" button yet (it's a known, tracked feature request). Until that ships, running Fireshare yourself in the bundled Portainer is the supported workaround: 1. Open Portainer from the dashboard's Apps page (port 9000; the admin password is in state/portainer-admin-password.txt on the box if you need it). 2. Follow Fireshare's own install instructions for the image, environment variables and volumes — those are the source of truth for the app itself. 3. Two SparkBox-specific rules so nothing breaks or gets wiped later: • Give it a host port that no SparkBox app already uses (each app's port is shown on the dashboard). • Keep Fireshare's data and its compose files OUTSIDE the SparkBox install directory (e.g. /opt/fireshare). SparkBox only manages, updates and backs up its own install dir, so anything you run yourself stays yours — but that also means SparkBox won't update or restart it for you. That's the whole recipe. If you'd also like Fireshare reachable through the dashboard's links / reverse proxy alongside the other apps, say so and I'll give you the sbproxy network step. Feel free to paste the compose you plan to use and I'll sanity-check it before you deploy.
HBCharles wrote:
thanks, yes i'd like it to be reachable through the dashboard and have the reverse proxy so its accessible outside of my network like other apps. the compose is from the site, as below version: "3" services: fireshare: image: shaneisrael/fireshare:latest-lite containername: fireshare ports: - "8080:80" environment: - ADMINUSERNAME=admin - ADMINPASSWORD=admin - ENABLETRANSCODING=true volumes: - ./fireshare/data:/data - ./fireshare/processed:/processed - ./my/videos/folder:/videos - ./my/images/folder:/images
Chris wrote:
Compose looks solid. Two adjustments for the reverse proxy: 1. Add the sbproxy network. In your compose add: networks: sbproxy: external: true And in the fireshare service add: networks: - sbproxy 2. Create the Nginx Proxy Manager entry (Apps menu, Nginx Proxy Manager, Host, New Proxy Host): - Domain name: fireshare.mydomain.com - Scheme: http - Forward Hostname: fireshare - Forward Port: 80 - Check Block Common Exploits and Websockets Support - SSL: Request a new SSL Certificate for HTTPS Change ADMINUSERNAME and ADMINPASSWORD from admin/admin before deploying.
Chris wrote:
HBCharles — I gave you the Portainer workaround to deploy your custom app. Did you get a chance to try it? If you ran into any issues with the compose configuration or Portainer deployment, let me know what error you got and I'll help troubleshoot.