I have a feeling that this human step might be at the end of a chain of automated filters.

No, only the local FS. But they have recommendations in their README for integrating with S3 with the help of other tools.

You are invited to join the CopyParty! This has a web UI accessible from the browser, also from mobile, files are stored directly on the filesystem (not encrypted or on a database) and you can mount it as a network drive on Windows and Linux. But it doesn’t let you sync files for offline use, at least not without the help of some auxiliary tools.

You won’t find anything simpler to install and configure than this.

Would you mind to share how to copy your setup? In particular how to mirror all your GitHub repos, do you have to manually add them to Gitea one by one?

Why would I want to spend my time with a game full of AI generation, when I could play one that had real actual people craft the work.

Because people have different skill sets, and I’d argue that for someone who has no skills in drawing, using AI as a tool to help add a little polish is not worse than pulling a generic already-seen asset pack from [your favourite game engine]'s marketplace. It all depends on how much, and how, AI is used.

Of course this only applies to indie developers and small studios. Big studios can afford to and should hire artists and designers.

Here’s my config for reference, which works for me:

name: forgejo
services:
  forgejo:
    image: codeberg.org/forgejo/forgejo:12
    environment:
      - USER_UID=1000
      - USER_GID=1000
    restart: always
    volumes:
      - ./data:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      #- 80:3000
      - 2222:22
    networks:
      - nginx
networks:
  nginx:
    name: nginx
    external: true

If you can share your error message we might be able to better pinpoint the issue.

EDIT: I searched a bit and now I understand better what you are trying to do. I didn’t know about this “SSH shim” idea. This is not what I have done on my setup, sorry.

If port-forwarding is an issue, you can always use a free VPN to reach your self-hosted services. Or if you want to make them public, you can set up yourself a relay on AWS LightSail for less than 5$/month. Or if you want to save as much as possible you can use TailScale or CloudFlare’s Zero Trust network to self-host for free using their server as a relay.

They provide decent defaults for all the not-so-straightforward configurations, and they provide a web UI to configure the rest. That’s the sole reason I would recommend it to get one’s feet wet without having to work too much.

If one is committed to do things “the right way” they could switch to Nginx and “proper” self-hosting later.

I would say this would be the proper way to do it (at least as a sysadmin), but since it’s OP’s first time I would simplify it to:

1. Install CloudFlare ZeroTrust daemon on your local server;
2. Set up reverse proxy such as Nginx (optional, the alternative is to use a different subdomain for each service, which might be easier);
3. Point the FQDN to CloudFlare.

Let CloudFlare handle the certificates, DDoS protection, etc… Link if you’d like to give this setup a try.