mirror of
1
Fork 0
Beyond coding. We forge.
Go to file
Earl Warren 7d8ae8279f
[BRANDING] parse FORGEJO__* in the container environment
(cherry picked from commit b075991747)
(cherry picked from commit da3f76228e)
(cherry picked from commit 20d196e74f)
(cherry picked from commit 0bf8b1824e)
(cherry picked from commit 655bb770a7)
(cherry picked from commit d69d5c2c46)
(cherry picked from commit 00b55e5a53)
(cherry picked from commit 456121fd8a)
(cherry picked from commit 9716a158e4)
(cherry picked from commit 7d60a6f511)
(cherry picked from commit d32a6d9437)
(cherry picked from commit ee1de38527)
(cherry picked from commit 54e7799d13)
(cherry picked from commit 4f04da7ab7)
(cherry picked from commit 0d39a0a520)
2023-10-23 15:04:12 +02:00
.devcontainer
.forgejo
.gitea [WORKFLOW] yaml issue templates 2023-10-23 14:16:24 +02:00
.github
assets
build
cmd [BRANDING] Rebrand dump log 2023-10-23 15:04:12 +02:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-10-23 15:04:12 +02:00
custom/conf
docker
docs
models [BRANDING] Use `forgejo` binary name 2023-10-23 15:04:12 +02:00
modules [BRANDING] parse FORGEJO__* in the container environment 2023-10-23 15:04:12 +02:00
options
public
releases/images
routers [BRANDING] Use `forgejo` binary name 2023-10-23 15:04:12 +02:00
services [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-10-23 15:04:12 +02:00
snap
templates [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-10-23 15:04:12 +02:00
tests [BRANDING] Update nodeinfo branding 2023-10-23 15:04:12 +02:00
web_src [v1.22] [BRANDING] Add Forgejo light, dark, and auto themes 2023-10-23 15:04:11 +02:00
.air.toml
.changelog.yml
.dockerignore
.editorconfig
.eslintrc.yaml
.gitattributes
.gitignore
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
CHANGELOG.md
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile [BRANDING] symlink gitea to forgejo in docker containers 2023-10-23 15:04:12 +02:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-10-23 15:04:12 +02:00
LICENSE
MAINTAINERS
Makefile [BRANDING] Replace branding in Swagger 2023-10-23 15:04:11 +02:00
README.md
RELEASE-NOTES.md
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
go.mod
go.sum
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-10-23 15:04:12 +02:00
package-lock.json
package.json
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml
vitest.config.js
webpack.config.js

README.md

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.

Learn more

Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.