![]() ![]() To do this, your server would need to be able to authenticate with your git provider.In addition to running composer, you would also need to run git to make commits and push to your repo.Your server many not even have Composer installed, or allow this kind of behavior.Composer is a CLI tool–you would have no capacity to troubleshoot or debug it from the admin, unless you built a system to do so (which would be a non-trivial undertaking).If the install fails, and especially if it fails in a partial state, your site is entirely broken.a package fails to install the server runs out of PHP workers and stalls composer runs out of memory, etc) The site could easily go down while the install is in progress (i.e.It’s a security risk (you’re effectively allowing someone to execute more-or-less arbitrary code on your server).If you want to maintain the Bedrock approach, someone adding a plugin via the admin would essentially be running a composer install on your live production server. ![]() ![]() You could potentially build a system to do this, but I would strongly recommend against it for the following reasons: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |