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
I was discussing Laradock with a colleague and in particular talking about how to install it, and we thought that for some projects, it might be convenient to be able to install it using Composer, along with all your other PHP dependencies.
Composer typically installs dependencies into the vendor folder, but can install to other folders in a project.
Having it managed by composer would certainly help with keeping everything up-to-date for devs across a team, as well as allowing us to upgrade it on a project branch, etc.
There are of course also plenty of good reasons for not managing it via composer; the most obvious being if you're running composer from inside your containers. Those projects could carry on installing Laradock the way they are doing now. But for those that it would benefit, please can this suggestion be considered.
The text was updated successfully, but these errors were encountered:
Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.
Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.
I was discussing Laradock with a colleague and in particular talking about how to install it, and we thought that for some projects, it might be convenient to be able to install it using Composer, along with all your other PHP dependencies.
Composer typically installs dependencies into the
vendor
folder, but can install to other folders in a project.Having it managed by composer would certainly help with keeping everything up-to-date for devs across a team, as well as allowing us to upgrade it on a project branch, etc.
There are of course also plenty of good reasons for not managing it via composer; the most obvious being if you're running composer from inside your containers. Those projects could carry on installing Laradock the way they are doing now. But for those that it would benefit, please can this suggestion be considered.
The text was updated successfully, but these errors were encountered: