Forgejo Gitea Migration — check your compose file free

This free tool flags Gitea and Forgejo tags and runner settings in Docker Compose files that need migration.

Forgejo Gitea Migration — check your compose file free
Example of the result this page gives you

Try it freeFull version · $29 →

How it works
  1. Put your own numbers into the free version below — no sign-up.
  2. Your result shows up right here, as you type.
  3. Want to keep it, print it or do it again next time? That is what the full version adds — see "What you get".

What you get: Export the dated two-hop migration report (Markdown + JSON) for the change ticket, one file per compose file in the workspace.

Try it freeFull version →

Forgejo migration lint for docker-compose files: flags Gitea tags past 1.22 (no transparent upgrade), a first hop that skips Forgejo v10.0, end-of-life Forgejo tags and Gitea act_runner. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Install free

Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.

VS Code Marketplace
ext install ReadyStack.forgejo-migration-check

Team? One key for every ReadyStack linter, 5 seats, $149 once

Get one email when this rule changes
We watch the regulation and vendor sources behind Forgejo Migration Check — Gitea 1.22 cutoff every day. When a rule changes, you get a single email with what changed and the updated check. No newsletter.
Forgejo Gitea Migration — check your compose file free
Example result

Get the full version $29

Export the dated two-hop migration report (Markdown + JSON) for the change ticket, one file per compose file in the workspace.

One payment, one licence key for this tool. The key is shown right after payment.

Gitea Enterprise lists $19 per user per month ($9.50 on a 1-year commitment) at about.gitea.com/pricing

Buy the full version — $29

Need more than this one? ReadyStack Pass opens all 679 files and 561 full versions — $29/month or $199/year. See the Pass →

Questions people ask

What does Forgejo Migration Check do?

It reads the image lines of a docker-compose or compose.yaml file and flags what breaks a Gitea to Forgejo switch: a Gitea tag past 1.22, a first hop that is not Forgejo v10.0.x, Forgejo majors past end of life on the Forgejo release schedule, unpinned tags, Gitea's act_runner and custom GPL builds. Each finding has a line number and the fix.

Who is Forgejo Migration Check for?

Self-hosting admins, homelab owners and DevOps teams that run Gitea with Docker or Podman compose and plan the move to Forgejo, plus agencies that maintain several client Git servers. It suits anyone who must know, before pulling a new image, whether the Gitea data can go to Forgejo without manual database edits.

Why not just read the free Forgejo docs?

The Forgejo upgrade guide and release schedule are free and correct, but they do not read your compose file. Docker will pull forgejo:11 onto a Gitea data volume without a warning, and a floating gitea:latest tag moves past 1.22 on the next pull. The check compares every image line with those published rules and dates.

What is free in Forgejo Migration Check and what is paid?

Free: the VS Code extension and the web page check any compose file with all eight rules and show every finding with its fix, no key needed. Paid, $29 once for one licence key per person or team seat: export a dated two-hop migration report in Markdown and JSON for the change ticket, one file per compose file in the workspace.

What does paid Gitea support cost instead of moving to Forgejo?

Gitea Enterprise, the vendor's paid support plan, lists $19 per user per month, or $9.50 per user per month with a one-year commitment, on about.gitea.com/pricing. Staying on Gitea is a valid choice; this check is for teams that have decided to move to Forgejo and want the upgrade path verified line by line before the switch.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Privacy: your e-mail is used only to send you the answer. A question appears on this page only after it is answered, without your e-mail.

Embed this tool on your site (free)

Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.

 All embeddable tools

For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →

ENDEJAESPT

Find a tool

For a team or company: for an invoice with your company details, a quote or several licences, write to support@getreadystack.com.

Who is behind this page

ReadyStack is a small team. We build each tool for one job people keep asking about, from the rules and sources named on the page, and we run it on the worked example you see here before it goes live.

How we check our pages: each rule names its source and the day we read it.

Something looks wrong, or you are stuck? Write to support@getreadystack.com or use the contact form. It goes to our own inbox, not to a bot.

About ReadyStack

New this week

More in Developer tools See all →