Josh Koenig

No sure how I feel about having non-secret things in `secrets.json`. It's not really meant to be a config system. Further, in my experience real world implementations often have multiple...

@stevector Thanks for your comments. The vision is right on, but: > Of course Quicksilver as a whole is still evolving. And maybe for the stage we are at now...

Currently quicksilver operations are limited to a 120 second timeout. If you're not getting results, that's likely the reason why. I think it's far to say we should make that...

> I know I should be able to trigger this using the UI, but for some reason it doesn't work on all my sites. By any chance do the sites...

> No. The options are there. They just don't work. Some urls are replaced, some are not. When I run a search-replace with terminus it replaces the rest of them...

This is now partially fixed. We are handling timeouts properly internally. Still work to do in order to get the timeouts to be presented nicely in the Terminus `workflows --watch`...

For now we are trying to steer away from premature abstraction, or the presentation of anything "library esque" in Quicksilver. It's early days. I'd prefer having one big file to...

Some platforms (like ours) bundle a CDN as part of their value, so I appreciate it being included. :)

`terminus auth machine-token-generate` +1 for specificity.

`terminus auth generate-machine-token` +1 for grammar! :)