Scott Walkinshaw

> I'm not sure though if this would solve the problem, or if ansible.cfg is "safe" to edit w/o breaking future Trellis updates. It would likely fix it (as a...

I was thinking about this again and there's two ways to work around this: 1. modify `ansible.cfg` and remove the `vault_password_file` setting 2. set the `ANSIBLE_ASK_VAULT_PASS=true` env var (you could...

Gimme some example outputs of what we should display

Makes sense 👍 I'd have to look around since I don't know much about Go testing

The simplest possible implementation here would be to run `ssh user@server "tail -f /srv/www/site/logs/*"` to output all logs. There could be flags for access/errors only. We could potentially leverage the...

This is a good point... it's tough to have a nice UI while also displaying all relevant info. And in this case pip's normal output is not very nice, so...

@dalepgrant forgot to ask, but with your setup you have no distinction between environments right? If so, you can just use `development`: ```bash trellis provision --extra-vars ansible_limit=server1 development ``` The...

Completely agreed. This would be a great feature for trellis-cli 👍 I'm familiar with the Rails upgrade task and it could work like that: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#the-update-task ```shell $ rails app:update identical...

This PR caught me while I was away on vacation so it got lost in the shuffle. Despite this being a limitation of Capistrano, I'd be open to potentially including...

Looks interesting. README needs a rebase now