PHP sury afterhand activation #46
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: evolix/ansible-roles#46
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If one tries to activate PHP sury while PHP is already installed, the new PHP version is never installed and the task fails.
Ideally, enabling sury would force the reinstall of PHP.
The main problem becomming how to keep the right PHP version when re-rolling the playbook. I fear the very nature of the sury repository makes idempotent behaviour more difficult.
Don't use php-foo package. Instead, aim for the php7.X-foo packages
Then you'll know the exact version installed, so the right Apache Module to enable, the right path for configurations, etc...