wintercms / cli Goto Github PK

Would be pretty wicked if the tool could have a flag to update itself automatically from github releases.

Mercator from Discord suggested a great feature - a migrate command to automatically switch an October website over to Winter.

We could possibly do the following:

• Run a check to make sure a compatible version exists
• Switch out the Composer dependencies
• Adjust the bootstrap/autoload.php file
• ....
• Profit? (not monetarily, but from goodwill for converting another happy user to Winter CMS)

It would be great if we could get rid of the current PHP CLI installer and instead have something based on Composer like laravel new $dir is (https://laravel.com/docs/7.x/installation#installing-laravel), including how they have you install the helper.

Eventually I'd also like to be able to tweak the installation after it's pulled from composer to make my recommend changes for a new project (I.e. modify README, get rid of .github and other October specific project files that don't apply to any projects that use the october repo as a base, tweak .gitignore, setup .env.example, etc). Basically the key points from my https://gist.github.com/LukeTowers/9100845ba50bd53d957da822d06f3b56#file-setupproject-sh. I'd be fine with october new ?$project basically being an alias for composer create-project, but then have the advanced setup behind a flag or something.

winter:manifest should be removed from the Winter core entirely since it's only for maintainers to use to update the central build manifest and relocated to the winter-cli.

winter:version should be reimplemented within winter-cli with support for identifying October CMS down to v1.0.319 and Winter from 1.0.472 & 1.1.2. This will enable developers to quickly identify the exact version (and any changed module files) of any pre-existing October / Winter instances that they may come across.