Feature/optimize docs #7
Conversation
| # | ||
| # If running your commands in a simple `sh` is not enough you could | ||
| # launch your favorite shell as well to leverage more complex tasks | ||
| watch: zsh -c "source ~/.zshrc && nvm use && npm run watch" |
There was a problem hiding this comment.
Seems like it would be kinda nice to be able to configure the shell that should be used to start commands. Should be fairly easy, no?
There was a problem hiding this comment.
yeah, kind of. I think we have to configure the paths/names of the rc files for several popular shells.
But I think the via actions could get way slower because sourcing large/complex rc files is not for free. At the moment I would leave the trade-off to the user even it is more complicated to opt-in. But if we would source the files automatically we should have to design an opt-out.
There was a problem hiding this comment.
Yeah, I though of adding options to opt in to a specific shell on different levels, e.g. globally (in a new via.yaml), or on project level, or on service level
|
Those are some great changes! I agree, that we should release when we merge this. |
Co-authored-by: Paul Mohr <p.mohr@sopamo.de>
I've added some docs for some advanced actions and a rough term explanation.
Would be happy of you could skim over it.
I think we should merge this together with the next release because the docs are referring to shell args.