You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to detect vagrant or lima automatically in most cases (by looking into the .trellis directory).
If both vagrant and lima configuration is present, it probably should assume vagrant (backwards compatible).
Possibly an additional command trellis vm logs would make sense for this edge case.
Summary
trellis logs development
should adjust (omit) the ssh user automatically when using lima.At the moment, the ssh user is hardcoded to
vagrant
when the environment isdevelopment
:https://github.com/roots/trellis-cli/blob/master/trellis/ssh.go#L10-L11
It should be possible to detect vagrant or lima automatically in most cases (by looking into the
.trellis
directory).If both vagrant and lima configuration is present, it probably should assume vagrant (backwards compatible).
Possibly an additional command
trellis vm logs
would make sense for this edge case.Additional context
Output when running
trellis logs development
:Command needed to get the logs:
Or enter the vm using
trellis vm shell
and tail from inside.The text was updated successfully, but these errors were encountered: