RC deploy via composer

[luckyraul]

With this config Magento2 core modules do not copy to their folders

"require": {
        "magento/product-community-edition": "2.0.0-rc",
        "magento/magento-composer-installer": "*",
        "php": "~5.5.0|~5.6.0|~7.0.0"
    },
    "extra": {
        "magento-root-dir": "public/",
        "magento-force": "override"
    },
    "minimum-stability": "alpha",
    "prefer-stable": true,
    "autoload": {
        "psr-4": {
            "Magento\\Framework\\": "public/lib/internal/Magento/Framework/",
            "Magento\\Setup\\": "public/setup/src/Magento/Setup/"
        }
    }

same config worked well with beta6

[mazhalai]

@luckyraul we have changed how magento is deployed via composer. Now modules will not be marshaled anymore and will work fine from any location, as long as a component is properly registered. Please see this documentation for more details. Also, for better understanding of why this change was made, please read through all comments in this thread.

[luckyraul]

It's okay to load from vendor, but now I get this error after clean install

"Cannot read contents from file "/var/www/shop.stagingxxx.net/releases/7/public/var/www/shop.stagingxxx.net/releases/7/vendor/magento/
module-ui/view/base/ui_component/etc/definition.xml" 
Warning!file_get_contents(/var/www/shop.stagingxxx.net/releases/7/public/var/www/shop.stagingxxx
.net/releases/7/vendor/magento/module-ui/view/base/ui_component/etc/definition.xml): failed to open stream: No such file or directory"

[luckyraul]

It's a problem of getting the relative path from the vendor folder inside Magento\Framework\Filesystem\Driver\File

[mazhalai]

@luckyraul there is an issue with relative paths, please see this comment for more details. Workaround is to ensure

There is a known restriction that files currently must be under Magento base directory.

[luckyraul]

That's it, thanks.