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 would love to see the option to jump into a site shell from the terminal which you can do already once you have opened a shell from the app dashboard and run the generated shell script that local creates for that site.
Example:
ID
Name
Status
2DYPBV1dU
sandbox
started
local-cli shell 2DYPBV1dU would effectively be launching the shell script found in .../Local/ssh-entry/2DYPBV1dU.sh using the same hash ID you would use to start and stop the site.
This would allow me to remain within the terminal, start a local site, jump into that site shell, perform actions using wp-cli, and then exit the shell, and stop a site without ever having to touch the app itself. This could be made further useful with some automation scripts to help folks who use local in their daily work to test various projects locally before pushing changes to other repositories or out to staging sites.
The text was updated successfully, but these errors were encountered:
I would love to see the option to jump into a site shell from the terminal which you can do already once you have opened a shell from the app dashboard and run the generated shell script that local creates for that site.
Example:
local-cli shell 2DYPBV1dU
would effectively be launching the shell script found in.../Local/ssh-entry/2DYPBV1dU.sh
using the same hash ID you would use to start and stop the site.This would allow me to remain within the terminal, start a local site, jump into that site shell, perform actions using wp-cli, and then exit the shell, and stop a site without ever having to touch the app itself. This could be made further useful with some automation scripts to help folks who use local in their daily work to test various projects locally before pushing changes to other repositories or out to staging sites.
The text was updated successfully, but these errors were encountered: