Cherry picking ideas for 2.x -> 3.x

[beporter]

For my own reference, see here: #16 (comment)

Everyone else is welcome to add additional suggestions for useful things to migrate from the old 2.x skeleton into the new 3.0 skeleton. I'd personally place a priority on ease-of-conversion and overall value.

[beporter]

Moving the list of ideas for things to pull up from Cake 2 land into Cake 3 land here:

• README.md (standardized documentation template)
• .gitignore (vagrant/puppet/bin-scripts additions)
• .editorconfig (defaults mostly for not screwing up .yaml files)
• .travis.yml (Loadsys standard build settings)
• bootstrap.sh (convenience wrapper for Loadsys devs to clone and prep the project after initial creation)
• composer.json (bin scripts, coding standard, phpdoc, phpcs)
• Gruntfile.js (test watcher and asset build tooling) See Import/upgrade basic grunt tools into 3.x skeleton. #129
  • package.json (node tools)
  • Console/node/ (grunt tooling)
• Vagrantfile + Lib/puphpet/ folder (vagrant VM)
• Config/core.php (loading env-specific configs)
• Config/database.php (loading env-specific configs)
• Config/phpdoc.xml (documentation build settings) No issue created yet.
• Config/phpunit.xml (unit test settings)
• Test/Case/All*.php (suites for running tests in batches) Might want to consider a suite for controller "unit" tests vs "integration" tests.
• webroot/_pi.php (standardized, hardened phpinfo script)
• webroot/robots.txt (actually providing a sane robots file out of the box) _Needs to be imported from 2.x branch.
• Running composer exclusively in the VM: Inside the VM, symlink the /var/www/Vendor folder to a non-shared (VM-internal-only) folder such as /var/composer/Vendor and then run all composer commands from inside the VM. Since composer wouldn't be installing deps to a shared folder (that would exhibit poor I/O performance) it should run quickly enough.