Here is a short summary of the issue I faced (if it can help other packagers).
Previously (packaging v1) home directory of forgejo user was set to the data dir (/home/yunohost.app/forgejo)
With packaging v2 the resources.system_user which is in charge of creating the forgejo user cannot use an environment variable to set the home directory. So I decided to let the default value (/var/www/forgejo aka install directory) which is quite fine.
I just add a mv command in the upgrade script to move .ssh directory to its new location.
But with this correct configuration forgejo still create its .ssh directory in the old home directory (/home/yunohost.app/forgejo) . Therefore the ssh access still didn’t work.
I found the mistake : it remained in the systemd service file, a HOME environment variable set to /home/yunohost.app/forgejo. That’s why forgejo used to create .ssh in this directory instead of its real home directory. I deleted this config, which is a legacy from the Gitea fork.
@snm Sorry to abuse of your time, but if you can make again the test of the upgrade process, and try to push a repo, it will be great.
(testing branch is ready)
Hello, must be my guest.
I found it was a problem with the portal sso. I don’t remember how and why I have commited in the nginx file the line include conf.d/yunohost_panel.conf.inc;
and also sometime it have again this trouble, I have to delete cookies and datas on the web navigator and it comes back…
I have also this issue with Gitea, also I have try install another Gitea instance and again can’t have admin page… Sorry, to related this, but it means is not only a Forgejo bug…