Description

Installs a minimal functional HTTP application using the Antidot framework. It starts defining the workflow for all other profiles, like manipulating composer.json, creating boilerplate code, deleting unneeded files, etc.

How has this been tested?

Is covered by unit tests, and is tested manually.

• Unit tests

vendor/bin/phpunit --textdox

• Manual Tests

• Install Web profile in a different path from the skeleton app.

• Install Web profile in a different path from the skeleton app with a different namespace.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.