Spell out that running gitea with your own user is unsupported #62
Conversation
|
For added discoverability for people having the same issue (but not knowing that it is because of Gitea), maybe the error message should be included also, namely |
| @@ -38,6 +38,7 @@ The goal of this project is to make the easiest, fastest, and most painless way | |||
|
|
|||
| - A cheap Raspberry Pi is powerful enough for basic functionality. | |||
| - 2 CPU cores and 1GB RAM would be the baseline for teamwork. | |||
| - Gitea is supposed to be run with a separate dedicated non-root user account on UNIX systems, no other mode of operation is supported. (**NOTE**: in case you run it with your own user account and the built-in SSH server disabled, Gitea modifies the `~/.ssh/authorized_keys` file, so you will **not** be able to interactively log in.) | |||
There was a problem hiding this comment.
separate dedicated? I would prefer just dedicated, than I'm fine with this change.
There was a problem hiding this comment.
oh totally agreed, plus there is an unneeded comma too
|
LGTM |
|
It's a pity to not support running from own user, if we can document all the issues it's better, or is it only the ssh keys ? (that "regenerate keys" command could be made safer) |
|
@sztanpet Can you also update the other language documents? |
|
No sorry, I do not know the other languages |
|
@sztanpet OK. |
|
LGTM |
|
Could you send another PR to back port to 1.0? |
|
there it is |
|
There is an open issue to resolve this issue. Until than we will have this phrase which is warning the users. |
I just wanted to run gitea in the easiest way possible, so I ran it with my own user only to find
that I could no longer log in with SSH anymore.