Getting gogs backup

[ntnsndr]

I'm trying to migrate Gogs to Gitea. I've had too many issues with the limitations of Gogs and need something a bit more fully featured.

I'm trying to follow these instructions but am getting stuck on the attempt to create a backup file:

root@90d8b446-14e3-45a1-87e0-e669aa2581c0:/home/git/gogs# ./gogs backup
2024/04/16 16:54:13 [ WARN] Custom config "/home/git/gogs/custom/conf/app.ini" not found. Ignore this warning if you're running for the first time
2024/04/16 16:54:13 [FATAL] [gogs.io/gogs/gogs.go:40 main()] Failed to start application: init configuration: create SSH root directory: mkdir /root/.ssh: read-only file system
root@90d8b446-14e3-45a1-87e0-e669aa2581c0:/home/git/gogs# mkdir /root/.ssh
mkdir: cannot create directory ‘/root/.ssh’: Read-only file system

How can I run this backup command in the Cloudron terminal environment?

Apologies for my ignorance, and thank you in advance.

[ntnsndr]

I'd also be grateful for any other tips on how best to migrate from Gogs to Gitea.

[ntnsndr]

Update. I got some guidance on getting this running from the Gitea Cloudron docs, but I am still getting an error when trying to create a backup:

root@90d8b446-14e3-45a1-87e0-e669aa2581c0:/home/git# sudo -u git /home/git/gogs/gogs backup /run/gogs/app.ini 
2024/04/16 19:07:56 [ WARN] Custom config "/home/git/gogs/custom/conf/app.ini" not found. Ignore this warning if you're running for the first time
2024/04/16 19:07:56 [FATAL] [gogs.io/gogs/gogs.go:40 main()] Failed to start application: set engine: create 'xorm.log': init: init file "/home/git/gogs/log/xorm.log": open file "/home/git/gogs/log/xorm.log": open /home/git/gogs/log/xorm.log: no such file or directory

[girish]

@ntnsndr It seems the CLI wants GOGS_CUSTOM env var. I have set this in the latest package.

After updating it, can you try https://docs.cloudron.io/apps/gogs/#cli ?

[ntnsndr]

@girish Thank you, that worked. Though now I'm realizing that I'm not sure if this migration process will work, because the Gogs version we are running is newer than the upgrade process allows:( But glad we can now run these commands.