When I first installed the file browser I was able to view volume 2 which is where I have my media folder. But now I am only able to view the volume that has ugos and I can’t figure out how to access volume 1 and volume 2.
7 replies
Chris wrote:
Hey jackhammer57 -- you haven't done anything wrong here. A few days ago the File Browser app itself got swapped out for a newer version under the hood, and that swap only carries over your main SparkBox folder, not any extra volumes you'd browsed to before -- so volume 2 dropping out of view lines up with that change, not something you broke. There isn't a way to add it back yourself from inside File Browser right now. I've flagged this for Tom so he can look at properly supporting a second volume.
Chris wrote:
Heads up — 1.6.542 just shipped and should cover what you reported here. You can grab it straight from the dashboard: Settings → Updates → Update SparkBox. Let me know if that sorts it, or if you're still hitting it. (Prefer the terminal? sudo sparkbox upgrade — note update only refreshes app images and will not move you to a new release.)
jackhammer57 wrote:
I have updated to latest version of sparkbox but cannot figure out how to access my other drives from file browser.
Chris wrote:
Good — being on the latest is the right start, but that update only makes the second-drive feature reachable again; it doesn't re-add volume 2 on its own. There's no dashboard button for it yet, so it's a two-file edit over SSH. 1. Create /opt/sparkbox/state/overrides/files.yml: yaml services: filebrowser: volumes: - /volume2/your-media:/folder2 Swap in your real volume-2 path. 2. Edit /opt/sparkbox/state/filebrowser/config.yaml and add a second entry, - path: /folder2, under its sources: list. 3. Run sudo sparkbox restart files. Both drives then show up as separate folders. If you'd rather not hand-edit YAML, just say so and I'll flag it for Tom.
jackhammer57 wrote:
just confirming I have the steps right. first shut down filebrowser then sudo nano /opt/sparkbox/state/overrides/files.yml: services: filebrowser: volumes: - /volume1:/ssd - /volume2:/raid sudo nano /opt/sparkbox/state/filebrowser/config.yaml sources: path: /ssd path: /raid then sudo sparkbox restart files
jackhammer57 wrote:
I did the following and it's still not showing. if I'm reading it correctly the config.yaml states that editing post install does nothing. sudo nano /opt/sparkbox/state/overrides/files.yml services: filebrowser: volumes: - /volume1:/ssd1 - /volume2:/raid sudo nano /opt/sparkbox/state/filebrowser/config.yaml GNU nano 7.2 /opt/sparkbox/state/filebrowser/config.yaml drive/volume — see docs/PER-APP-OVERRIDES.md. This tracked file itself is never read again after the first seed, so editing it post-install does nothing; it only matters for brand-new installs. Everything else install-specific (admin password, JWT secret, database path) still arrives via environment variables in the module compose. server: port: 80 cacheDir: /home/filebrowser/data/tmp sources: - path: /folder config: defaultEnabled: true - path: /ssd1 config: defaultEnabled: true - path: /raid config: defaultEnabled: true
jackhammer57 wrote:
update. it did work after all. they show up in a dropdown box