You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have an issue when upgrading the version of PHP, Which I think is due to a mix match between the vagrant config an the virtual machine. When I update PHP by sshing into the VM everything works fine. The issue occurs when starting the box back up/provisioning which breaks my site every time. Heres a part of the error I'm getting:
TASK [Install Composer libraries] **********************************************
failed: [site.test] (item=phpunit/phpunit:5.6) => {"ansible_loop_var": "item", "changed": false, "item": "phpunit/phpunit:5.6", "msg": "Deprecation Notice: Array and string offset access syntax with curly braces is deprecated in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSch...
This is what I'm running on the VM to update it... Like I said - It works perfectly before it breaks
I have tried commenting out the part where the composer stuff runs which does stop the error from showing in the terminal however my site is still broken after. Is this a known error? You should be able to reproduce this easily, Its happened 100% of the time on my machine.
The text was updated successfully, but these errors were encountered:
Operating System: MacOS
Vagrant Version: 2.2.10
Virtual Box Version: 6.1.12
Hello, I have an issue when upgrading the version of PHP, Which I think is due to a mix match between the vagrant config an the virtual machine. When I update PHP by sshing into the VM everything works fine. The issue occurs when starting the box back up/provisioning which breaks my site every time. Heres a part of the error I'm getting:
This is what I'm running on the VM to update it... Like I said - It works perfectly before it breaks
I have tried commenting out the part where the composer stuff runs which does stop the error from showing in the terminal however my site is still broken after. Is this a known error? You should be able to reproduce this easily, Its happened 100% of the time on my machine.
The text was updated successfully, but these errors were encountered: