Thanks for your feedback. Making it easier to use the Indigo services on the command line is a high priority for me. At present I maintain a bunch of EXPORT commands for myself, which I then paste into a terminal session eg for PHP
export PATH=~/.indigo/stacks/YOUR_STACK_UUID/php_UUID/bin:$PATH && \
export PHPRC=~/.indigo/stacks/YOUR_STACK_UUID/php_UUID/etc/php.ini && \
export PHP_INI_SCAN_DIR=~/.indigo/stacks/YOUR_STACK_UUID/php_UUID/etc/conf.d
If you use the above you'd need to replace the UUIDs of course, even though that info takes some skill to find inside ~/.indigo/stacks. This has worked ok for me, but is very clumsy, so I'd like to automate it so you can click a button in Indigo and have it set up a terminal session with all the right PATHs.
Alternatively, I do really like the Lando approach here... I haven't used Lando personally, so was unaware until @soniktrooth showed me how you can prefix commands with lando and it will run the command inside the container. However, I'm not really sure that's feasible in a reliable fashion outside of container-land. I guess it could run the commands inside a subshell or such, I'd have to experiment pretty thoroughly with that. Very open to more knowledgeable input on that front.
I am also playing with the idea of having a preference setting where you can choose one of your installed PHPs as a global one, and have Indigo write that to your .profile. Problem is, I'm not sure whether it should be in .profile, .zshrc, .zprofile or what! I can't really assume people are even using zsh... so I'm a bit undecided on the best way forward with the shell integration at this stage. Thoughts gratefully accepted!
Re composer and drush, with the EXPORTs above run inside a terminal session, you can install composer and drush either locally or globally, and run them simply using composer or drush with no command prefix or anything else.
Sorry it's a bit convoluted at present. Let me know how you go!