Posts by votdev

    The fact that I'm sure is :
    - they have exactly the same nginx/proxy config files.
    - this morning, I update from v5.6.20 to v5.6.21 the first server; reverse proxy stopped just after (<1 min).
    - this afternoon, I updated the second server, reverse proxy stopped just after (<1 min).

    If you have not pressed the Apply button in the UI then nothing should have happened. The latest version 5.6.21 has marked the nginx, host and postfix modules as dirty, thus their configuration is re-deployed on pressing Apply. But there are no changes in the code, except that the IPv6 detection has been improved/fixed, thus it can happen that now only IPv4 configuration is generated if IPv6 is not configured.

    The indention is wrong. Please have a look into YAML or SaltStack documentation about that issue.


    Code
    append_custom_hosts:
    file.append:
    - name: "/etc/hosts"
    - text: {{ hosts }}

    Is that something that you could add in OMV (5 or 6) ?

    It's not trivial; otherwise the UI would already support custom rules. IMO the UI is good for what it is intended for; a simple UI for simple rules. Special purposes can be implemented manually by the user via custom workflows that are supported by Debian.


    But it's free to the community to contribute this feature to the project.

    As you may have realized the new UI is named Workbench as tribute to the best home computer ever: Amiga

    And the Amiga Workbench has this mouse cursor while loading. So please see it as it is, a tribute and nostalgic remembrance.

    The problem will be fixed in the next release of the mergerfs plugin, see https://github.com/OpenMediaVa…lt-mergerfsfolders/pull/8.

    Maybe there is an alternative (i.e. REST service) to query/trigger apt?

    The UI already uses something equivalent; RPC, known long before REST becomes popular. But i don't think this is something for common users.


    However you twist and turn it and build a better API, finally this would not bring any benefit because a REST or RPC endpoint will simply call the usual APT commands which results into the same output and behaviour.

    Clearing the browser cache should fix that. You could also reload the page multiple times to fix that.


    One question, do you have installed plugins that have entries in the 'Storage' menu?