There is some things that is a bit bad with Volumio, and had bee from beginning.
The dev page. You can not see configuration, for example if SSH is on. Why not put some css on the page at least, so you can see what you clicked on.
When you done some config by your self on files in the system, you have to do Firmware reset to get updates to next version. You have to do al configuration from the start again, even reninstall all plugins. Why not restrict to some critical system files, so you can get update. Quite frustrating when you’re on testing (I am on 4 beta).
Why is it not possible to get a backup in (on the plugin for backup), after upgrade, so at least can get back plugins and the NAS configuration?
Might be use full if there is enough demand. They just did something similar to the Volumio update channel (Alpha/Test/Stable)
Volumio 4 Beta is built on a new foundation: Debian Bookworm, which introduces major architectural changes. To ensure stability and compatibility:
The partition layout has changed, and older layouts can’t support OTA updates properly.
Custom system-level changes (like editing config files) can interfere with the update process, especially when overlays or critical boot files are involved.
Volumio uses a read-only root filesystem for reliability, which makes it hard to preserve manual tweaks across updates.
So when you modify system files, Volumio can’t guarantee a clean update path. That’s why it forces a firmware reset, to avoid bricking the system or introducing subtle bugs.
For plugin settings you have the folder /data/INTERNAL. Where settings for Peppy, FushionDSP, Now Playing, … are stored. If you back them up, you can restore them.
The MPD database is very tricky to backup/restore and not fool proof.
Well, I been on Volumio, 2, 3 and now on 4. Been the same on my topics above, since the beginning, so hav nothing to do with Debian Bookworm.
It is ok that it overwrite config files on updates, but why do you need to do a Firmware reset ? Just tell user that the files will be over-written on update and then let the user be able to bring in a backup, after the update.
Might also bee quite good for peoples willingness to be engaged in a beta development.
Well, in case you know so well, why not join the Volumio Development team and discuss a redesign of the architecture . Sure they will understand they did it all wrong.
Why do you think yo need to do a redesign of the architecture, to get my suggestions to work, on the problems and what do you actually mean by doing a redesign of the architecture? May bee the problem is that is not fully open source, instead.
I do not know enough to be part of development team, I know basic Linux and Debian, though, so I can see the problems. Do you mean that you have to be a fully participant in the development to see the problems and sugest solutions, or what is your point?
