suggestions for improvement for the docker images of MinimServer

[simoncn]

(16-03-2025 18:17)airflow Wrote:  I understand your sentiment. But on the other hand it destroys the elegance of being able to deploy a licensed in an automated way. I have an idea for a compromise: If you would make it possible to define the license information via environment variables, it could work that in this case when you connect for the first time, you are greeted with a screen which shows the already entered license information and just prompts you to confirm.

MinimServer doesn't use environment variables for configuration. Also, this doesn't feel like a good way to pass sensitive confidential information.

What is the scenario when something like this is required? I would expect creating a new licensed container to be an infrequent event as the number of licensed containers that can be in use is limited to the license device limit (3 or 5). Once created, a licesnsed container should usually not be destroyed because this would cause its license activation to be lost. If this is the case, entering license information using copy and paste when the container is first started doesn't seem to me to be too onerous.

Quote:I am referring to this discussion.

Thanks for this.

Quote:I think activating the correct, complete configuration for MinimServer should possible to be done in a more automated way as well.

I normally do it by pasting the prepared configuration into mscript like this:

Code:

cat /Music/minimconfig/minimserver2-config.mscript | /opt/minimserver/minimserver-2.2/bin/mscript

But I cannot really automate this step (in the course of creating the container), because the instance first has to be licensed before it accepts the confguration. So it becomes now two manual steps (1. license and 2. configuration).

Using profiles solves this problem. A profile file can contain properties that need a full license as well as properties that don't. Here is an example:

Code:

contentDir = /opt/Music
+tagOptions = Album.ignore.sort={A, The}
.profileVersion = 2.2

You can import and select this profile using a starter license. At this stage the tagOptions setting is not enabled. When a full license is activated, this enables the tagOptions setting.

Quote:Docker offers healthchecks which can be already defined in the published images of MinimServer. It's possible to define them later individually by the administrator, but it could be already included.

For example, it could be something like a simple check whether a

Code:

echo about | /opt/minimserver/minimserver-2.2/bin/mscript

returns (contains)

Code:

MinimServer is running

Thanks for clarifying. It seems that MinimServer already provides commands that can be used for this.

Please bear in mind that MinimServer supports many platforms and it is not feasible to provide deep platform-specific integration with all features of all platforms.