Connect self-hosted Gitea repository to Railway (non-GitHub source)
anwerhanik
PROOP

2 months ago

Hello Railway team,

We are running a self-hosted Gitea instance (git.shozzle.com) as our internal source of truth. Due to company policy, we cannot use GitHub as the primary repository.

We would like to understand the supported ways to deploy from a self-hosted Git provider (Gitea) to Railway.

Current situation:

  • Repos are hosted on self-managed Gitea (behind Cloudflare Tunnel + SSO)

  • GitHub auto-deploy works, but we want to avoid GitHub

  • SSH access is restricted by Cloudflare Tunnel (no raw TCP)

  • HTTPS Git access is available with tokens

Questions:

  1. Does Railway support connecting directly to self-hosted Git providers (e.g., Gitea) for auto-deploy?

  2. If not, what is the recommended approach?

    • Railway CLI (railway up)?

    • Deploying from a Docker image registry?

  3. If Docker image is recommended:

    • Which registries are officially supported (GHCR, Docker Hub, private registry)?

    • Can Railway pull from a private registry using credentials?

  4. Are there any plans or workarounds to support non-GitHub Git providers natively?

We’re happy to adjust our pipeline based on Railway’s recommended best practice.

Thanks in advance for the guidance.

$10 Bounty

1 Replies

Railway
BOT

2 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway • about 2 months ago

douefranck
FREE

2 months ago

hey,

railway only supports github for git auto-deploy, not gitea or other self-hosted git providers.

your two options:

option 1: railway cli run railway up from your local machine or ci pipeline. no github needed, pushes code directly to railway. simple for manual deploys or scripted in gitea actions

option 2: docker registry better for auto-deploy build image in gitea ci/cd, push to supported registry like docker hub, ghcr, gitlab registry, quay.io, or mcr. railway pulls and deploys automatically. private registries require pro plan and you add credentials in service settings

verified registries from docs: username/repo for docker hub ghcr.io/user/repo for github packages registry.gitlab.com/user/project for gitlab quay.io/user/repo for quay

for your https git plus cloudflare tunnel setup, docker registry approach is cleanest since railway cant connect directly to your gitea anyway

no native gitea support planned that i can find in docs

Loading...