I guess some way to load host keys that you've pre-validated?
Instead of https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/branch/main/ssh_config.tmpl
I guess some way to load host keys that you've pre-validated?
host means "where the git repository is" which is where you'll make a ssh connection (based on the private Git remote) and be asked to verify the host key. atm we're just saying "anything goes" but it would be better to explicitly allow host keys in the .ssh/config so that we are cloning from where we expect to clone from.
`host` means "where the git repository is" which is where you'll make a ssh connection (based on the private Git remote) and be asked to verify the host key. atm we're just saying "anything goes" but it would be better to explicitly allow host keys in the `.ssh/config` so that we are cloning from where we expect to clone from.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Instead of https://git.coopcloud.tech/coop-cloud/parasol-static-site/src/branch/main/ssh_config.tmpl
I guess some way to load host keys that you've pre-validated?
What does
hostmean in this context? The server that an app instance of this is deployed to?hostmeans "where the git repository is" which is where you'll make a ssh connection (based on the private Git remote) and be asked to verify the host key. atm we're just saying "anything goes" but it would be better to explicitly allow host keys in the.ssh/configso that we are cloning from where we expect to clone from.Support host key checkingto Support git repo host key checking