-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Include --work-path flag in commands in authorized_keys #15978
New issue
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
Conversation
It looks like the tests are failing a comparison check. Can you please update them? 🙂 |
Sorry about that, I neglected to run |
I'm really not certain that this is necessary. Why are you needing this? Gitea Serv and Hook shouldn't really need any thing that depends of AppWorkPath. Could you please explain |
I explained in the linked issue. gitea definitely needs to know where my repositories are, and in the default config, those are defined relative to AppWorkPath.
…On May 26, 2021 2:57:10 PM EDT, zeripath ***@***.***> wrote:
I'm really not certain that this is necessary.
Why are you needing this? Gitea Serv and Hook shouldn't really need any thing that depends of AppWorkPath.
Could you please explain
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#15978 (comment)
|
Fix go-gitea#15595 Replaces go-gitea#15978 Signed-off-by: Andrew Thornton <[email protected]>
I've made a PR that makes the authorized_keys command a template - allowing you to add work-path or other things as needed |
Fix #15595 Replaces #15978 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: techknowlogick <[email protected]>
Closing per merge of linked PR |
Fix go-gitea#15595 Replaces go-gitea#15978 Signed-off-by: Andrew Thornton <[email protected]> Co-authored-by: techknowlogick <[email protected]>
Fixes #15973