Hello, I'd like to know where are sparkbox files installed and if there is a way to chose the pool where it's installed. Thank you
4 replies
Chris wrote:
SparkBox itself stays at /opt/sparkbox. On UGREEN, the bulky data defaults to /volume1/sparkbox-data, with media under /volume1/sparkbox-data/media. You can choose another pool by setting SBDATADIR and MEDIAROOT to paths on that pool in /opt/sparkbox/.env, then running sudo sparkbox up. If you already have files on volume1, tell me which pool you want before changing it—the setting changes where apps look, so the existing library should be moved carefully rather than blindly.
mdma wrote:
Thank you for your reply. At first I was confuses because sparkbox was installed on the UGOS disk (the one soldered to the NAS). Then I managed to uninstall it following the ssh command found on the guides (even if at the end it didin't uninstall completely). After that I did an installation on my volume 1, i found a reply on a post in the community section indicating a command to change installation location. Now it is correctly installed on my Nvme drive (volume 1) on my docker file. I still have one question. How can i edit .env file before installation (for future attempts)?
Chris wrote:
Good question: .env does not exist until the installer creates it, so for a future install you pass the storage path into the installer instead of pre-editing the file. For volume 1, use: curl -fsSL https://get.tomsparkbox.com/install.sh | sudo env SBDATADIR=/volume1/sparkbox-data bash -s -- --nas On UGREEN, keep the SparkBox program itself at /opt/sparkbox; that avoids UGOS share-folder permissions resetting the program files. SBDATADIR puts the large data on your selected pool. After installation, the file is /opt/sparkbox/.env; edit it with sudo nano /opt/sparkbox/.env, save, then apply changes with sudo sparkbox up. Replace /volume1/sparkbox-data if you want another pool. You do not need to uninstall again just to edit settings, and moving an already-populated data directory should be planned rather than done by changing the path blindly.
Chris wrote:
Apologies for catching you in the wrong thread — your Tom AI one will not take another reply from me until you post in it again, and this correction should not wait. There I told you to run sudo sparkbox update to pick up the fix for the stuck Unlock AI button. That was wrong: update only refreshes your apps' images and cannot move your box onto a newer SparkBox release, which is where that fix lives. Run sudo sparkbox upgrade instead — it preserves your settings, data and app config — then hard-refresh the dashboard once. Nothing here changes the install-location advice above.