axyr/silverstripe-modulefolder

Install modules in the 'modules' folder instead of root

silverstripe-modulefolder

Install modules in the 'modules' folder instead of root., _(*1)

This is not really a module, but more a proof of concept., _(*2)

It might break things, but first attempts seem to work just fine., _(*3)

I tested the silverstripe installer with a few modules and the build passed:, _(*4)

https://travis-ci.org/axyr/silverstripe-installer, _(*5)

https://github.com/axyr/silverstripe-installer, _(*6)

• axyr/silverstripe-adminlogin
• ajshort/silverstripe-gridfieldextensions
• unclecheese/display-logic

Please help me testing this with your own modules ! :), _(*7)

As far as I can see, the only thing that needs to be changed is an extra check for an extra path in Requirements::path_for_file. To test this without touching core there is a ModuleRequirements_Backend that also search for requirements in MODULES_DIR, _(*8)

if(!Director::fileExists($fileOrUrl)) {
  $fileOrUrl = MODULES_DIR . '/' . $fileOrUrl;
}

Composer

With composer you can set custom installer-paths for silverstripe-module types. To leave the cms and framework folder in the root you can force that as well., _(*9)

Example:, _(*10)

{
    "name": "silverstripe/installer",
    "description": "The SilverStripe Framework Installer",
    "require": {
        "php": ">=5.3.2",
        "silverstripe/cms": "3.1.2",
        "silverstripe/framework": "3.1.2",
        "silverstripe-themes/simple": "*",
        "axyr/silverstripe-modulefolder": "*",
        "axyr/silverstripe-adminlogin": "*"
    },
    "config": {
        "process-timeout": 600  
    },
    "minimum-stability": "dev",
    "extra": {
         "installer-paths": {
            "cms/": ["silverstripe/cms"],
            "framework/": ["silverstripe/framework"],
            "modules/": ["axyr/silverstripe-modulefolder"],
            "modules/{$name}/": ["type:silverstripe-module"]
        }
    }
}

This still leads to a code folder near th other modules in the modules folder, but that's something we can't avoid right now., _(*11)

Background

I like to have thirdparty modules living in their own folder and keep my own custom application code in mysite or maybe even a second folder with custom code., _(*12)

Now that we have composer I install more modules which sometimes provide little functionality but can come in quite handy. I don't want all those small 'plugins' in my root folder., _(*13)

I don't want to stir up the discussion again if we need this or something is wrong with the current 'all code in root folder' approach, _(*14)

There was a long debate in the Silverstripe 2.x era on the Google dev group:, _(*15)

https://groups.google.com/forum/#!msg/silverstripe-dev/6qdRkCDliEg/A3mH9kFhG6MJ, _(*16)

and, _(*17)

https://groups.google.com/forum/#!topic/silverstripe-dev/on1_ABPDNTc, _(*18)

For now I just want to know if this is gonna work!, _(*19)