Node.js and PostgreSQL update

[tomfrenzel]

Hi @CodeWithCJ!

I'm currently building a Proxmox Helper Script to install Sparky Fitness in an LXC without docker and have some questions about its dependencies.

I see that Node.js 20 is currently being used in the Dockerfiles but Node.js 25 is listed as a dev dependency in the frontend package.json. So I did some testing and found that both the frontend and backend seem to build and function flawlessly on Node 25. Is there a specific reason the image is staying on v20 for now, or is it just a roadblock?

Likewise, I was wondering whether there are any plans to update the PostgreSQL version as well at some point since the latest version is now 18.

There aren't any issues with the current versions (other than Node 20 being EoL) and everything is running fine 😄 I was just wondering if there might be reasons why those dependencies have not got raised yet

[CodeWithCJ]

I have to admit, I wasn't aware Node.js versions were out of sync 😄. I will sync them.

Regarding PostgreSQL, I wanted to upgrade but due to other priorities didn't look into it yet. And also haven't explored how to safely upgrade.

When your Proxmox script is ready, please let me know and we will link to community doc section. The one I have hasn't been updated for several months. As I don't use Proxmox, this is never been tested.

https://github.com/CodeWithCJ/SparkyFitness/blob/main/proxmox_sparkyfitness.sh as I don't use Proxmox.

[tomfrenzel]

I have to admit, I wasn't aware Node.js versions were out of sync 😄. I will sync them

No worries, Sounds good!

Regarding PostgreSQL, I wanted to upgrade but due to other priorities didn't look into it yet. And also haven't explored how to safely upgrade.

I think that's fine for now as PostgreSQL 15 is still supported until November 2027. I tested a fresh installation with 17 and it worked just fine. But i have no clue how to update a PostgreSQL DB Docker container to a new version. In a bare bones PostgreSQL install there are migration commands but for Docker you probably would need to update the compose file and then run the migration command upon fist start of the new container.
Sounds complicated to me 😆

I think I'll just stick with PostgreSQL 15 for the script and once you updated the compose files to use a newer version, I'll update my script to do so as well.

When your Proxmox script is ready, please let me know and we will link to community doc section

Will do 😉

[tomfrenzel]

@CodeWithCJ The script is now available: https://community-scripts.github.io/ProxmoxVE/scripts?id=sparkyfitness 😉

[apedley]

This is huge for the project! I've used proxmox community scripts many times. Thanks @tomfrenzel

[CodeWithCJ]

@tomfrenzel Awesome. Could you share some insights on what changes in SparkyFitness could break the your script?
New mandatory env variables and anything else that you can think.

[tomfrenzel]

I think the main thing that could break the script is the .env.example file.
During install, the script uses the example file and replaces all parts that need custom values. So if there are new required variables, that could be problematic. Since this replacement is not done during updates, new required variables would not find their way into existing installations.
But if you already know, that the config is going to change a lot in the next time, i can also add the replacement part to the update function 😉 For new required variables that need to be changed to a custom value (eg. some sort of secret), I'll need to update the script. In that case it would be nice of you can give me a ping before the release. Although I'll look out for such changes by myself as well 😄

[CodeWithCJ]

I will try to keep you posted. Though I want to limit and get rid of as much as env variables as possible, some prefer env variables. So we might have few coming up for OIDC #598

[tomfrenzel]

Sounds good! If those variables are all optional, the script won't be affected.