That’s actually a great thing.
Nowadays I often find myself in a situation when the actual fix in the code takes 5 minutes but following all the routine to deploy it takes half an hour. And I can imagine how much effort would it take to add all the bells and whistles to an open source package. So it’s a great thing, op par wot Rector in terms of reducing the boilerplate effort.
I didn’t test it but even if there are some childhood diseases, they surely can be cure in the process. Great job!
ok I’m really glad for this comment, would be happier if you have time to look it up. I mean nothing special but having setups up and running and ready to add your credentials/keys/username etc. I actually created this for myself because of the reason you mentioned and then thought about sharing this with the community.
This looks great. Have you done anything like a survey of competing projects and the advantages and disadvantages of PHP Noise! in comparison?
You mean like https://github.com/PHPExpertsInc/skeleton ?
Travis-CI support
PHPUnit
phpstan
Dockerized PHP stack (mariadb/postgres, redis, nginx, PHP)
PHP-CS-Fixer with PSR-12
Property .gitattributes for composer packages not including useless bloat
CodeClimate test code coverage metrics
Psalm support
Seems extremely similar, actually. Can I like merge my .gitattributes and codeclimate support and isDebugOn() testcase into your project so I can then abandon mine?
Members
Online