Repository files navigation

繁體中文 |简体中文

The goal of this project is to make the easiest, fastest, and mostpainless way of setting up a self-hosted Git service.

As Gitea is written in Go, it works acrossall the platforms andarchitectures that are supported by Go, including Linux, macOS, andWindows on x86, amd64, ARM and PowerPC architectures.This project has beenforked fromGogs since November of 2016, but a lot has changed.

For online demonstrations, you can visitdemo.gitea.com.

For accessing free Gitea service (with a limited number of repositories), you can visitgitea.com.

To quickly deploy your own dedicated Gitea instance on Gitea Cloud, you can start a free trial atcloud.gitea.com.

You can find comprehensive documentation on our officialdocumentation website.

It includes installation, administration, usage, development, contributing guides, and more to help you get started and explore all features effectively.

If you have any suggestions or would like to contribute to it, you can visit thedocumentation repository

From the root of the source tree, run:

TAGS="bindata" make build

or if SQLite support is required:

TAGS="bindata sqlite sqlite_unlock_notify" make build

Thebuild target is split into two sub-targets:

• make backend which requiresGo Stable, the required version is defined ingo.mod.
• make frontend which requiresNode.js LTS or greater.

Internet connectivity is required to download the go and npm modules. When building from the official source tarballs which include pre-built frontend files, thefrontend target will not be triggered, making it possible to build without Node.js.

More info:https://docs.gitea.com/installation/install-from-source

After building, a binary file namedgitea will be generated in the root of the source tree by default. To run it, use:

./gitea web

Expected workflow is: Fork -> Patch -> Push -> Pull Request

Translations are done throughCrowdin. If you want to translate to a new language, ask one of the managers in the Crowdin project to add a new language there.

You can also just create an issue for adding a language or ask on Discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty, but we hope to fill it as questions pop up.

Get more information fromdocumentation.

We provide an officialgo-sdk, a CLI tool calledtea and anaction runner for Gitea Action.

We maintain a list of Gitea-related projects atgitea/awesome-gitea, where you can discover more third-party projects, including SDKs, plugins, themes, and more.

If you have questions that are not covered by thedocumentation, you can get in contact with us on ourDiscord server or create a post in thediscourse forum.

• Maintainers
• Contributors
• Translators

Thank you to all our backers! 🙏 [Become a backer]

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

How do you pronounce Gitea?

Gitea is pronounced/ɡɪ’ti:/ as in "gi-tea" with a hard g.

Why is this not hosted on a Gitea instance?

We'reworking on it.

Where can I find the security patches?

In therelease log or thechange log, search for the keywordSECURITY to find the security patches.

This project is licensed under the MIT License.See theLICENSE filefor the full license text.