New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General hello world review (some bugs) #2
Comments
It doesn't pass to drush automatically. Try |
Also, the "ash" part of the alias is not required. You can just use @site.env. |
These all have the same error:
|
I'm assuming that it can't find the drush executable in the codebase
Is there an assumption about how drush is in the path once in that directory? |
I'm debugging locally as i'm sure there's something about my setup |
When i run it natively, the executed command is:
When i run it with ash the executed command is:
Note that my alias uses the |
It is just execs whatever is after the alias. You can try |
Ash runs in your alias root, which can be "web" or just git root. The command will be relative to that. So change your alias root or figure out how to change path to composer bin path. |
I guess i'm a bit confused at this point with all the various contexts ash/local/remote, and can't help but think i'm using it in a way that it isn't designed for.
(if i don't quote the command i get |
All of the sites that I have setup locally are hosted in different places for different clients (Platform.sh, Lagoon, etc), and I generally have a drush command that I can run on my host regardless of whether the local development environment (ddev, lando, etc, yes i use multiple) is running.
So my goal of using ash is to exectute a command on a remote site regardless of what i'm working on locally.
Setup
When i installed with composer globally, the I had to modify the PATH, and add:
export PATH="~/.composer/vendor/bin:$PATH"
rather thanexport PATH="$HOME/.config/composer:$PATH"
. I don't have a$HOME/.config
directory.I also had to add the directory
~/.ash
because adding the initial site aliases resulted in this error. This went away when i manually added the directory.After I'd added a couple of sites I get two files which looks pretty good:
I then followed the advice to
Call 'ash @foo' to access the site
, so i swtiched to my home directory and ran itBut all that said,
ash ls
now shows me 6 aliases (expected).Running a command
In one of my projects there is a site alias file
./drush/sites/self.site.yml
that points to a Platform.sh environment and it looks like this:And normally I can run it like this from the codebase that contains the alias.
So the goal is to run it from another location. However, when i run it with ash, I get this error:
The text was updated successfully, but these errors were encountered: