Jørn Lindberg
Jørn Lindberg
I have the same issue with permission denied
I have 50 hosts and I will not accept such a manual process for a service intended to automate tasks as a solution. It is at best a temporary workaround....
Update on that, if you disable hostkey checking, it will ad the host to your well-known and then you can re enable it again
> > Update on that, if you disable hostkey checking, it will ad the host to your well-known and then you can re enable it again > > Not for...
Got around this by just using the openid config as this is more "clean" See: https://github.com/alerta/docker-alerta/issues/463#issuecomment-2025882219
+1 Would really appreciate OpenID
> @theparthacus Thanks for showing upstream activity on this issue. > > > > If I may ask, as many like me will be curios, is there a rationale behind...
I was looking at maybe going to OpenProject, but even with a name like that they sadly suffer from the same issue. I think it also is weird that they...
My workaround was to use an access token So like `https://:@git.net/path/to/your/repo` How to set one up: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
I have the same issue however I am using the binary build, and If I try to add it to the config it just gets deleted