Please, web app developers, consider how your users will upgrade. If your upgrade process is "remove the old one, unzip the new one", then it's not an upgrade process. It's an encouragement to never upgrade.
I can integrate it in my app to deploy it in production.
I need to have a git repo on the server (mainly for private repo). And it configurable with y'all config.
But with a cli command, the component will:
creates an export of given tag
extracts it in some place
runs composer install
can run some other commands
copies secret files into app dir
create a symlink (for apache)
In case of problem, I redo a symlink on previous version
Doing some #PHP package maintenance tonight, this dev dependency bump kinda stood out 😅 . Mainly I make sure my packages work on the latest #PHP versions, either through support requests or when I run into issues myself. Most of my packages are designed with the future in mind.
The long-term plan is to get reusable workflows for every package and #Renovate to open PR's more aggressively than #dDpendabot to uncover potential future issues. Currently rolling that out with every package I
#PHP 8.4 introducing "Property Hooks". This means you will be able to hook into the default read and write behavior of your class properties. The design also allows for more hooks in the future. Really looking forward to this one!
