Note that that only added three files: the composer.json file, the .editorconfig file, and the .gitattributes file. I suspect we could move the last two out of the root with some cleverness...
[x] Add a .gitignore
[x] Create composer.json that pulls in km-collaborative.
[x] Ran into this problem where you can't re-run composer install.
Added the $settings['skip_permissions_hardening'] = TRUE; value to my settings.local.php file. If we're deploying to Pantheon via circle, interesting to see what will need to happen with that. Circle can maintain that setting, but Pantheon needs to have the files be locked. Might be able to overwrite that specific file as well?
[x] Update the README below the "Delete me" line to be relevant to what we actually do. This will involve figuring this out.
[x] Start moving pieces out of this repo and into km-collaborative.
[x] Test: Do commit your composer.lock file on child sites but not on the km-collaborative site.
composer create-project --prefer-dist --no-install drupal/recommended-project my_site_name_dir
Note that that only added three files: the
composer.json
file, the.editorconfig
file, and the.gitattributes
file. I suspect we could move the last two out of the root with some cleverness....gitignore
$settings['skip_permissions_hardening'] = TRUE;
value to my settings.local.php file. If we're deploying to Pantheon via circle, interesting to see what will need to happen with that. Circle can maintain that setting, but Pantheon needs to have the files be locked. Might be able to overwrite that specific file as well?composer.lock
file on child sites but not on the km-collaborative site.Documentation improvements
terminus --version
. Add help if it's at a lower version.terminus build:project:create -h
and say to use 2.xFigure out why the new start project fails
This ticket is done when