-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Symfony 7 #238
Comments
Notice that this is currently blocked by |
It's pity. |
I install cachetool as a phar using my server provisioning tool and never have dependency issues.. Just an idea for anyone who's stuck. Because imo this has nothing to do with the application, it's a deploy-time utility. At least the way i use it. |
Yeah, we also went with the Phar release in the meantime with a few extra steps to have it available as usual everywhere. |
Any news? |
No. I installed Phar release as described above, it solved problem. |
consolidation/self-update 3.x does support Symfony 7, but it doesn't have a stable release yet. |
The ideal distribution of cachetool is via a phar file, not a dependency to your symfony project. |
@gordalina that depends on how you use it. In some cases you need to invoke it from PHP code in response of some events happened in your system. |
You can still invoke the phar from php, either using exec/proc_open style or even including it using phar://cachetool.phar/vendor/autoload.php to make its classes available that should mostly work but a bit more risky as you might have conflicting class versions then between your project and the phar. |
consolidation/self-update 3.0.0 has been released, so I assume this can be fixed now? |
Symfony 7 has been released and the Cachetool should be updated to support this new major version.
Maintainer's note:
The text was updated successfully, but these errors were encountered: