gitea on homeserver

• app
  • service
  • deployment
  • db secret
  • db config
  • disable registration DISABLE_REGISTRATION
• db
  • service
  • deployment
  • secret
    • 1password
  • config
  • backup cron
• nginx
  • http
  • ssh -> failed could
    • https://stackoverflow.com/questions/71789156/how-to-redirect-ssh-requests-in-nginx

sudo mkdir -p /opt/gitea/tmp  /data/gitea/gitea /opt/gitea/db-data /data/backups/gitea

sudo chown tjen:tjen -R /opt/gitea /data/gitea /data/backups/gitea

sudo find /opt/gitea -type d -exec sudo chmod 755 {} +
sudo find /data/gitea -type d -exec sudo chmod 755 {} +
sudo find /data/backups/gitea -type d -exec sudo chmod 755 {} +

 tree /{data,opt,data/backups}/gitea

gitea ssh failure

port forward straight to gitea 2224:22 worked port forward to nginx 2224:224 did not work (where nginx was stream{} configured to pass to gitea:22) for some reason, nmap on homeserver also did not show port 2224 open (earlier it did show 2222 open, when I was trying with that port…)