We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using lando ssh into the cli container, the user's $HOME is set to /home
lando ssh
cli
$HOME
/home
This doesnt play ball with the symlinking that occurs in
cli/plugins/lando-core/scripts/user-perms.sh
Lines 56 to 67 in 7325253
Net result is: git config --global --list
git config --global --list
fatal: unable to read config file '/home/.gitconfig': No such file or directory
Its a nice subtle detail to have the users .gitconfig available in the cli :)
I've locally got around this by putting the following into /scripts for my lagoon builds (non-clobbering):
/scripts
#!/bin/sh set -e if [ ! -f $HOME/.gitconfig ] && [ -f /user/.gitconfig ]; then ln -sf /user/.gitconfig $HOME/.gitconfig fi if [ ! -f $HOME/.ssh/known_hosts ] && [ -f /user/.ssh/known_hosts ]; then ln -sf /user/.ssh/known_hosts $HOME/.ssh/known_hosts fi
But maybe theres a better place to integrate this?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using
lando ssh
into thecli
container, the user's$HOME
is set to/home
This doesnt play ball with the symlinking that occurs in
cli/plugins/lando-core/scripts/user-perms.sh
Lines 56 to 67 in 7325253
Net result is:
git config --global --list
Its a nice subtle detail to have the users .gitconfig available in the cli :)
I've locally got around this by putting the following into
/scripts
for my lagoon builds (non-clobbering):But maybe theres a better place to integrate this?
The text was updated successfully, but these errors were encountered: