You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A self-hosted, privacy-first alternative to MyFitnessPal. Track nutrition, exercise, body metrics, and health data while keeping full control of your data.
@MickLesk / @CrazyWolf13 Is there a predefined way to increase the LXC resources during build and update? Normally this LXC woild only need 1 Core/1G RAM but i need double that when building the Frontend / Backend code
@CrazyWolf13 I tested the script with Node 25 as well as with PG 17. Both seem to not cause any problems.
For the Node version i think it's safe to update. But I'm not sure whether using PG 17 over 15 is a good idea. Theoretically SparkyFitness could use PG commands that are available in PG 15 but not anymore in 17.
@CrazyWolf13 The owner responded and will update the Node version in the Dockerfiles. For the PG version, it's not a priority to him yet and he isn't sure on how he would update it so existing installations won't break.
I'll create a PR to use Noe.js 25 then and will stick to PG15 for now unless @MickLesk as a different opinion on that
Thanks, yes always better to have it official from the dev!
The PG update goes okay for me, there is still over 1.5 years of support left, though ideally it will be updated and communicated early enough, so if you could keep an eye on this, it would be awesome!
I tested a bit more and found an issue with the data directory. I can't configure custom locations for the uploads and backup folder as the options in the .env are only used by the original docker-compose.yaml and not by the actual app.
So the directories are always /opt/sparkyfitness/SparkyFitnessServer/uploads/ and /opt/sparkyfitness/SparkyFitnessServer/backup/. Should i create symlinks to the /var/lib/sparkyfitness directory or just backup and restore that data in those directories during an update?
I'm not quite sure what's the preferred way here
The .env.example was made to work with docker. So some variables do not get passed into the container but are used only in the docker-compose.yaml like this:
volumes:
- ${SERVER_BACKUP_PATH:-./backup}:/app/SparkyFitnessServer/backup # Mount volume for backups
- ${SERVER_UPLOADS_PATH:-./uploads}:/app/SparkyFitnessServer/uploads # Mount volume for Profile pictures and excercise images
The only variables from .env.example that do not get passed into to the container are those: DB_PATH, SERVER_UPLOADS_PATH and SERVER_BACKUP_PATH.
So for our script, changing those does not affect the services
Hm, this values are not Part of the source Code. Only env or docker-compose, so this f.e. doesnt Work?
"SERVER_UPLOADS_PATH=/opt/sparky_data/uploads" ?
May you can add an request in there repo, with an Link to this issue.
Normally, all docker-compose env or normal env should be resolved in the service when called, docker doesn't really do it any differently. Either an implementation is missing, or the name is modified internally, or the paths are always fixed and the env have no influence.
DB, so i think, If pg17 Work flawlessly - better use this.
I can also try 18 so there is even more time until users will have to upgrade. The only risk is, that sparkyfitness currently uses psql statements that don't work with anything above 15. But that risk exists for 17 as well
The sparkyfitness script is ready for testing: bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/sparkyfitness.sh)"
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Activity
tomfrenzel commentedon Feb 16, 2026
PR is coming in the next couple of days
tomfrenzel commentedon Feb 16, 2026
@MickLesk / @CrazyWolf13 Is there a predefined way to increase the LXC resources during build and update? Normally this LXC woild only need 1 Core/1G RAM but i need double that when building the Frontend / Backend code
MickLesk commentedon Feb 16, 2026
Nope only with app-update.sh
tomfrenzel commentedon Feb 16, 2026
Alright. Then I'll check that out and see if i can do something similar
tomfrenzel commentedon Feb 20, 2026
@CrazyWolf13 I tested the script with Node 25 as well as with PG 17. Both seem to not cause any problems.
For the Node version i think it's safe to update. But I'm not sure whether using PG 17 over 15 is a good idea. Theoretically SparkyFitness could use PG commands that are available in PG 15 but not anymore in 17.
What do you think?
CrazyWolf13 commentedon Feb 20, 2026
Can you make a request on their repo?
or search for existing discussions on this?
EDIT: okay seems PG 15 is supported for another year, so it may not be that problematic, but what do you mean @MickLesk ?
tomfrenzel commentedon Feb 20, 2026
Yes, i just opened a discussion as no one else seemed to have asked anything similar yet 😄
tomfrenzel commentedon Feb 20, 2026
@CrazyWolf13 The owner responded and will update the Node version in the Dockerfiles. For the PG version, it's not a priority to him yet and he isn't sure on how he would update it so existing installations won't break.
I'll create a PR to use Noe.js 25 then and will stick to PG15 for now unless @MickLesk as a different opinion on that
CrazyWolf13 commentedon Feb 20, 2026
Thanks, yes always better to have it official from the dev!
The PG update goes okay for me, there is still over 1.5 years of support left, though ideally it will be updated and communicated early enough, so if you could keep an eye on this, it would be awesome!
tomfrenzel commentedon Feb 20, 2026
Will do 😉
tomfrenzel commentedon Feb 21, 2026
I tested a bit more and found an issue with the data directory. I can't configure custom locations for the
uploadsandbackupfolder as the options in the.envare only used by the original docker-compose.yamland not by the actual app.So the directories are always
/opt/sparkyfitness/SparkyFitnessServer/uploads/and/opt/sparkyfitness/SparkyFitnessServer/backup/. Should i create symlinks to the/var/lib/sparkyfitnessdirectory or just backup and restore that data in those directories during an update?I'm not quite sure what's the preferred way here
MickLesk commentedon Feb 21, 2026
But envs in docker compose are the Same Like our env in Services? Does did Not Work? 😅
tomfrenzel commentedon Feb 21, 2026
The .
env.examplewas made to work with docker. So some variables do not get passed into the container but are used only in thedocker-compose.yamllike this:The only variables from
.env.examplethat do not get passed into to the container are those:DB_PATH,SERVER_UPLOADS_PATHandSERVER_BACKUP_PATH.So for our script, changing those does not affect the services
MickLesk commentedon Feb 21, 2026
Hm, this values are not Part of the source Code. Only env or docker-compose, so this f.e. doesnt Work?
"SERVER_UPLOADS_PATH=/opt/sparky_data/uploads" ?
May you can add an request in there repo, with an Link to this issue.
Normally, all docker-compose env or normal env should be resolved in the service when called, docker doesn't really do it any differently. Either an implementation is missing, or the name is modified internally, or the paths are always fixed and the env have no influence.
3 remaining items
tomfrenzel commentedon Feb 21, 2026
I wanted to use
/var/lib/sparkyfitness/uploadsand/var/lib/sparkyfitness/backup. But i can also use/opt/sparkyfitness_data/...EDIT: Went with backup and restore for now
tomfrenzel commentedon Feb 21, 2026
I can also try 18 so there is even more time until users will have to upgrade. The only risk is, that sparkyfitness currently uses psql statements that don't work with anything above 15. But that risk exists for 17 as well
tomfrenzel commentedon Feb 21, 2026
Done here.
tomfrenzel commentedon Feb 22, 2026
@MickLesk I think this script can be marked as ready to test now 😄
github-actions commentedon Feb 22, 2026
The sparkyfitness script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/sparkyfitness.sh)"Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
CerberusStyle commentedon Feb 22, 2026
Install, web UI and account setup work flawlessly, update function also working as expected.
github-actions commentedon Feb 22, 2026
A PR has been created for sparkyfitness: community-scripts/ProxmoxVE#12185
CrazyWolf13 commentedon Feb 22, 2026
appreciate the testing @CerberusStyle !
michelroegl-brunner commentedon Feb 23, 2026
Merged with #12185 in ProxmoxVE
github-actions commentedon Feb 23, 2026
Files deleted with PR #1502