search

FortAwesome / wordpress-fontawesome

Font Awesome Official WordPress Plugin
Other
57 stars 19 forks source link

update the composer.lock #152

Closed jasonlundien closed 2 years ago

jasonlundien commented 2 years ago

@mlwilkerson -- Rob and I were getting the wordpress dev up and running locally. And It would NOT let me move any further without updating this file.

robmadole commented 2 years ago

@mlwilkerson we were just using local dev and caught a problem. Jason and I were able to get it going far enough to accomplish our task. So this can defer until we need to cut a release.

mlwilkerson commented 2 years ago

Closing since I've merged in an alternative way of dealing with this. Turns out: what we needed was a more clear strategy for keeping track of php version specific composer configs that would run in the various development environment containers. And probably, the fact that there were some issues reported here had to do with using a version of php in the host environment that didn't match the version that would have been running inside the the container--and using this composer config. I've updated the DEVELOPMENT.md with more detailed explanation about dealing with various php versions--usually only within containers, not the host environment. And the new docker configurations use php version specific composer configs within each of those environments.