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
Every time I want to exec into a PHP container, I have to spin exec {container_name} sh.
Laravel's Sail has a command named shell and bash to quickly exec into the PHP container
I think it's pretty useful, we don't need to think about what container name every time we want to exec into a container
🏆 How to solve this problem
I see Laravel's Sail is handled by setting the APP_SERVICE env by default to know exactly what container to exec. Maybe we can go that way
Another solution is: We often name a PHP container something like api, php, workspace, app, ... We can use grep to filter the container name to know which container to exec. Like this
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
👉 Describe the problem
Every time I want to exec into a PHP container, I have to
spin exec {container_name} sh.Laravel's Sail has a command named
shellandbashto quickly exec into the PHP containerI think it's pretty useful, we don't need to think about what container name every time we want to exec into a container
🏆 How to solve this problem
I see Laravel's Sail is handled by setting the APP_SERVICE env by default to know exactly what container to exec. Maybe we can go that way
Another solution is: We often name a PHP container something like api, php, workspace, app, ... We can use grep to filter the container name to know which container to exec. Like this
Beta Was this translation helpful? Give feedback.
All reactions