upgrading from 0.9.22 to latest

[michabbb]

@jhuckaby again: you are cooking here, amazing, thank you so much for this incredible project ❤️ 💪

you did so many updates in the last time, it´s finally time to update, and i have seen you also updated the xysat script, so i would like to ask: what´s the best way to upgrade? is there any particular i have to take care of ? does the xysat update itself (automatically) ? 😏
i am using ghcr.io/pixlcore/xyops. thanks for any hint, advice, tip!

[jhuckaby]

Thank you for your kind words ❤️

The best way to upgrade both xyOps and xySat is right inside the UI! Just navigate to the "System" tab in the sidebar, and use these:

This also works for Docker installations, as it does a self-upgrade "inside" the container, then self-restarts (make sure you launched the container with the --restart unless-stopped flag -- it's added by default).

Good luck!

[jhuckaby]

Okay, that's cool. You don't have to use the self-upgrade buttons. I'm sorry -- I was only trying to help.

Pulling the latest Docker image works just fine too. Just make sure you have external storage or at least a volume bind mount for your storage and configuration directories. Also, if you care about your log files, might want to grab those before deleting the old container.

[michabbb]

Don't get me wrong, I am thankful for any tip, but your advice to "use self-upgrade" while using Docker is the worst advice you can give someone. Sorry 🙈, because you are literally saying, "It's okay to make changes that get lost as soon you remove/re-create the container" That's FATAL, and you should never do that - except when debugging or testing something 😏

[jhuckaby]

I'm obviously new to the Docker thing, but I'm learning fast 😊

[michabbb]

Hey, all good 🙂
And first of all: respect, you’ve built a really great piece of software. Honestly, I probably couldn’t do this without AI 😁

Sorry if my message came across as harsh or a bit like a lecture, that wasn’t my intention at all. I definitely didn’t mean to attack you or your work.

I just felt it was important to clearly point out the Docker best-practice aspect, especially since other people are reading this.
When using Docker, the update model is: update the image and recreate the container, not modify or update things inside the container. A self-update inside a container goes against that core concept and could easily mislead people who are still learning Docker.

That’s why I was a bit more direct than usual, purely for technical clarity, not on a personal level 🙂

So yeah: peace ✌️
And thanks again for building and maintaining the project!

[jhuckaby]

Thank you for the kind words and advice! I will not recommend the self-upgrade feature to Docker users any longer. That was just my total misunderstanding of how containers are supposed to be used.