Configurable package installer

YAML based project installer inspired by IceHawk installer and Koriym.PhpSkeleton, _(*1)

, _(*2)

Usage

require api-clients/installer

Add api-clients/installer to require of your composer.json., _(*3)

post-create-project-cmd

It is recommended to use the following post-create-project-cmd script. This is the bare minimum require for the installer to work. api-clients/skeleton for example also runs resource generation, code style fixes, and QA checks after install.:, _(*4)

{

    "scripts": {
        "post-create-project-cmd": [
            "ApiClients\\Tools\\Installer\\Installer::postCreateProject",
            "composer update --no-autoloader --ansi",
            "composer update --ansi"
        ]
    }
}

installer.yml

Create an installer.yml in the project root of the package you want to create use the installer for. The following configuration is from api-clients/skeleton:, _(*5)

package: api-clients/skeleton
text:
  welcome: "Welcome to the API Clients new client installer."
  ascii_art_file:
    - ascii.small.art
    - ascii.medium.art
    - ascii.large.art
  ascii_art_package: api-clients/branding
config:
  current_ns: "ApiClients\\Skeleton"
  current_ns_tests: "ApiClients\\Tests\\Skeleton"
  require:
    - installer
    - installer-client-operations
  scripts:
    - post-create-project-cmd
questions:
  author_name:
    description: "Author name"
    question: "What is your name?"
  author_email:
    description: "Author email"
    question: "What is your email address?"
    validate: "Assert\\Assertion::email"
  package_name:
    description: "Your package"
    question: "What is your package name?"
    default: "vendor-name/package-name"
  path_src:
    description: "Your project sources location"
    question: "What is your project sources location?"
    default: "src/"
  path_tests:
    description: "Your project tests location"
    question: "What is your project tests location?"
    default: "tests/"
  ns_vendor:
    description: "Your namespace"
    question: "What is your vendor namespace?"
    default: "MyVendor"
  ns_tests_vendor:
    description: "Your test namespace"
    question: "What is your vendor test namespace?"
    default: "MyVendor\\Tests"
  ns_project:
    description: "Your project namespace"
    question: "What is your project namespace?"
    default: "MyProject"
operations:
  - "ApiClients\\Tools\\Installer\\Operation\\ComposerJson::create"
  - "ApiClients\\Tools\\Installer\\Operation\\UpdateNamespaces::create"

Lets break that down and describe what each section does:, _(*6)

package

The name of the skeleton package., _(*7)

text

Text options used to create a welcome at the start of the installer., _(*8)

text.welcome

Welcome message., _(*9)

text.ascii_art_file

Array with ASCII files., _(*10)

text.ascii_art_package

ASCII art package, if not provided the skeleton is searched for the ASCII art files., _(*11)

config

Array with additional configuration options., _(*12)

questions

The questions asked used for gathering the information needed to perform the operations., _(*13)

operations

Operations run after all the questions have been answered., _(*14)

License

The MIT License (MIT), _(*15)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:, _(*17)

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software., _(*18)

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE., _(*19)