For reducing traffic as well as speed issues, my company decided to mirror packagist.org/github with an internal satis composer repository.
When switching to this repo mirror, we noticed, that the setup of a neos-base-distribution has some problems. When accessing the neos backend via ://my-neos-url/neos, i get the following output, followed by a complete stacktrace.
Warning: md5*file(resource://TYPO3.Neos/Public/JavaScript/ContentModule-built.js): failed to open stream: "TYPO3\Flow\Resource\Streams\StreamWrapperAdapter::stream_open" call failed in /opt/neos/Data/Temporary/Development/Cache/Code/Flow_Object_Classes/TYPO3_Neos_Utility*BackendAssetsUtility.php line 52
This did not happen when the installation is done directly via github.
I did some research and finally figured out the problem.
In the typo3/neos repository you excluded the file "/Resources/Public/JavaScript/ContentModule-built.js", mentioned in the waring above. But this file is nevertheless part of your delivered source or .zip, and therefor part of a standard composer update via github.
The satis application on the other hand, unpacks the code and repacks it internally (i assume uses 'git archive tar'). In this process your definition in the .gitignore leeds to the deletion of this file, and breaks our setup.
I already know, how i can regenerate this via a grunt task, but this totally seems like a hacky workaround.
Please remove the ignore definition of "/Resources/Public/JavaScript/ContentModule-built.js", because this file is an essential part of the runtime.
Jira issue originally created by user jirgn:
For reducing traffic as well as speed issues, my company decided to mirror packagist.org/github with an internal satis composer repository.
When switching to this repo mirror, we noticed, that the setup of a neos-base-distribution has some problems. When accessing the neos backend via ://my-neos-url/neos, i get the following output, followed by a complete stacktrace.
This did not happen when the installation is done directly via github.
I did some research and finally figured out the problem. In the typo3/neos repository you excluded the file "/Resources/Public/JavaScript/ContentModule-built.js", mentioned in the waring above. But this file is nevertheless part of your delivered source or .zip, and therefor part of a standard composer update via github.
The satis application on the other hand, unpacks the code and repacks it internally (i assume uses 'git archive tar'). In this process your definition in the .gitignore leeds to the deletion of this file, and breaks our setup. I already know, how i can regenerate this via a grunt task, but this totally seems like a hacky workaround.
Please remove the ignore definition of "/Resources/Public/JavaScript/ContentModule-built.js", because this file is an essential part of the runtime.
Atachements:
Jira-URL: https://jira.neos.io/browse/NEOS-1885