mikeselander
commented
6 years ago A blocker to this is deciding where Chassis should go and how our projects should be organized. I've started on an example setup script and have made a good bit of progress, but where Chassis should reside affects how a setup script should behave.
On most projects that I've seen, we put Chassis into a chassis directory and use a local config file to setup a non-standard (to Chassis) folder structure, like such:
paths:
base: ..
content: contentHowever, doing a non-standardized folder structure has several issues. For example, Chassis doesn't respect configuration files in mapped folders, so you must handle moving files into other folders. Additionally, the Debugging extension simply doesn't install plugins when using a non-standardized setup.
Does anyone have any ideas on an HM-friendly directory structure without dealing with the problems of non-standard folder setup for Chassis? cc @BronsonQuick & @tfrommen.
Also ref #85
rmccue
The directory structure of HM Base makes it impossible to use the Chassis Quickstart instructions to set up a local development environment.
An install script should be added that helps with setting up Chassis, for single and multisite environments.