It might be nice not to need separate a separate SSH port just for Gitea; this is apparently possible through adding a `git` user and a helper script to the host: https://blog.sakuragawa.moe/gitea-in-docker-container-and-sharing-ssh-with-host/
This is actually what I did in the first iteration of trying out Gitea with Dokku. I found it tricky to manage because you have to setup a user account and a script to do the SSH connection threading. This more connection to the actual host filesystem which will be problematic for migrations. Unless you see some drawback of this, I would stick with it, the internal SSH server is quite convenient IMHO.
This is actually what I did in the first iteration of trying out Gitea with Dokku. I found it tricky to manage because you have to setup a user account and a script to do the SSH connection threading. This more connection to the actual host filesystem which will be problematic for migrations. Unless you see some drawback of this, I would stick with it, the internal SSH server is quite convenient IMHO.
This repo is archived. You cannot comment on issues.
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.
It might be nice not to need separate a separate SSH port just for Gitea; this is apparently possible through adding a
gituser and a helper script to the host: https://blog.sakuragawa.moe/gitea-in-docker-container-and-sharing-ssh-with-host/This is actually what I did in the first iteration of trying out Gitea with Dokku. I found it tricky to manage because you have to setup a user account and a script to do the SSH connection threading. This more connection to the actual host filesystem which will be problematic for migrations. Unless you see some drawback of this, I would stick with it, the internal SSH server is quite convenient IMHO.