construct
construct copied to clipboard
A PHP project/micro-package generator for PDS compliant projects or micro-packages.
Similar to [package-sync](https://github.com/spatie/package-sync) there could/should be a command to check a package for [PDS](http://php-pds.com/) compliance which could/should also [fix](https://github.com/spatie/package-sync#fixing-package-issues) found issues.
It would be nice to distribute `construct` via a PHAR file.
Maybe it would also be good to add support for [phing](https://github.com/phingofficial/phing) `build.xml` file?
When using the options `--github` or `--github-templates` a pre-populated [SUPPORT.md](https://github.com/blog/2400-support-file-support) file should be generated into the `.github` directory.
To also support users opting for `GitLab`, it would be useful to aid them in `constructing` a package structure targeted for GitLab. This could be done by introducing a `--profile`...
To also support users opting for `GitLab`, it would be useful to aid them in `constructing` a package structure targeted for GitLab. This could be done by introducing a `--profile`...
Support for using [gitlab-ci](https://gitlab.com/gitlab-org/gitlab-ci-yml/blob/master/PHP.gitlab-ci.yml) - as an alternative to travis-ci, when using GitLab
The `.construct` configuration should (also) be loaded from `$HOME/.config` and it should be recommended in the `README.md` to put it there instead of directly into `$HOME`.
Using the option to be e.g. `--parallel-lint` or simply `--lint` would add the [PHP Parallel Lint](https://github.com/JakubOnderka/PHP-Parallel-Lint) package as a development dependency, add related Composer scripts e.g. `lint` and `lint-changes`, and...
The generated Composer script _could_ be namespaced. With a new `--composer-script-namespace` option the namespace could be injected. When not set the Composer script namespace should be derived from the project...