DCA Hardened Git Server for Gitea (Arm64) — Support & Quick Start

At a glance

Quick start

This is the listing's usage information, verbatim. Every command in it is run by our QA on a freshly launched instance before an image version can publish, so the text and the tested procedure cannot drift apart.

After launch:

1. Connect over SSH as the opc user with the key you supplied at launch:

   ssh opc@PUBLIC_IP

2. Gitea runs as a systemd service on 127.0.0.1:3000. On first boot it creates the admin account and instance-unique secrets; check status:

   sudo systemctl status gitea

3. Read the generated administrator credentials (root only):

   sudo cat /root/.gitea_default_credentials

   You will be required to change the password at first login.

4. Reach the web UI safely by tunnelling over SSH:

   ssh -L 3000:127.0.0.1:3000 opc@PUBLIC_IP
   then open http://localhost:3000 and sign in as dcaadmin.

5. To expose Gitea beyond the instance (behind a TLS reverse proxy is recommended), rebind it to all interfaces and restart:

   sudo sed -i 's/^HTTP_ADDR = 127.0.0.1$/HTTP_ADDR = 0.0.0.0/' /etc/gitea/app.ini && sudo systemctl restart gitea

   Also set ROOT_URL under [server] in /etc/gitea/app.ini to the URL your users reach, so clone URLs are correct.

   Port 3000/tcp is already permitted in the host firewall. Restrict TCP 3000 in your VCN security list to the client CIDR; never expose an unproxied Gitea to the internet.

6. Clone and push over HTTP(S); Git over SSH is disabled (DISABLE_SSH = true in /etc/gitea/app.ini). Data (repositories + SQLite DB) lives in /var/lib/gitea; configuration in /etc/gitea/app.ini. Recommended sizing: at least 2 OCPU (4 vCPU) and 16 GB memory, scaling with repository count and CI usage.

The image is CVE-patched at build time. Apply ongoing updates with:

sudo dnf -y update

What the image provides

• Gitea 28.0.0, installed from the project's official signed binary with its SHA-256 checksum verified at build time, running as a dedicated unprivileged service.
• Fully self-contained: the built-in SQLite backend means no external database to provision. Launch one instance and you have a working Git server.
• Instance-unique security on first boot. A random administrator password and unique SECRET_KEY and INTERNAL_TOKEN are generated the first time the instance starts; nothing secret is baked into the image, and open registration is disabled by default.
• Loopback-bound by default; the web listener answers only on 127.0.0.1 until you place it behind TLS and open the port deliberately.
• Security hardening aligned to the Oracle Cloud Marketplace image standards: SELinux enforcing, host firewall default-deny with only SSH and the Gitea port permitted, no account with a usable OS password, no stray keys, and the image fully patched at build time.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or use the contact form. Include the listing name, your OCI region, the instance OCID and the output of sudo journalctl -u <service> -n 100 for the unit named in the quick start.

Gitea is a trademark of Gitea Limited. This image is an independent hardened distribution and is not affiliated with, endorsed by, or sponsored by Gitea Limited.