@ohadm2 not really 100% sure what you mean by that. Maybe you can explain in more detail. In general it doesn't sound like something we support though or plan to support.

Re the other points in the txt file:

1. A new option in the settings file that disables auto generation of JS Assets.
   This sounds like a Matomo issue. In general what you can do though is to execute these commands eg every hour and then the JS files will be generated on the server that you want:

MATOMODIR/console custom-piwik-js:update
MATOMODIR/console tagmanager:regenerate-released-containers

This will update all trackers and JS containers

2. A new option in the settings file that sets a custom location for JS Assets.
   This you could already do by specifying a config/config.php with eg such a content:

    'TagManagerContainerStorageDir' => function () {
        return '/tmp/alternative/path/';
    },

3. When the above options are on, no JS files will be generated and instead they will be pulled from the 'read/write' server using some sort of a infrastructure-based copy process. That way the 'read-only' server will be updated via the 'read-write' server and not via itself.

I don't understand what you mean here unfortunately.

Thanks for these interesting suggestions. That may help us in the future.

3. The idea here is to make the 'read/write' (a.k.a the back-end server) server the ONLY server that writes data. In such a case, every change in the UI will update only files inside this server. If another server is used as a front end for the system and only through that server system's resources (such as JS files etc.) are available anonymously thought the internet, it must be updated via some sort of sync process with the back-end server, otherwise it will hold different and out-dated files.

Thanks for the explanation, will move this to Matomo repo