1
0
Fork 0
Beyond coding. We forge. https://codeberg.org/forgejo/forgejo
Find a file
Loïc Dachary 1ba9e954e2
[BRANDING] add forgejo target to Makefile
The gitea target is kept as is, for the sake of compatibility with
build systems that rely on it. The forgejo target creates a hard link
with forgejo.

(cherry picked from commit ce156c7cb4)
(cherry picked from commit b2cb232825)
(cherry picked from commit 85543c22bd)
(cherry picked from commit 302955a20d)
(cherry picked from commit 4b1be0858e)
(cherry picked from commit afed1a6e20)
(cherry picked from commit e81304bcd1)
(cherry picked from commit 479cd51a03)
(cherry picked from commit 8baab7c0c1)
(cherry picked from commit 5d25ad9f09)
(cherry picked from commit f36942789f)
(cherry picked from commit 9abfbae8a0)
(cherry picked from commit 079e0efb01)
(cherry picked from commit 0f1b83005a)
(cherry picked from commit 3cc227aaff)
(cherry picked from commit 245310c682)
(cherry picked from commit 3f83e30c93)
(cherry picked from commit e2bdd6af3d)
(cherry picked from commit fb3ac3a20b)
(cherry picked from commit 0ffbd46032)
2023-12-11 15:42:59 +01:00
.devcontainer
.forgejo [UPGRADE] add sanity check for v1.20.5-0 2023-12-11 14:48:36 +01:00
.gitea [WORKFLOW] yaml issue templates 2023-12-11 14:48:36 +01:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-12-11 14:33:55 +01:00
assets [BRANDING] add Forgejo logo 2023-12-11 15:42:58 +01:00
build
cmd [BRANDING] Rebrand dump log 2023-12-11 15:42:59 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-12-11 15:42:59 +01:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-12-11 15:42:58 +01:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-12-11 15:42:58 +01:00
docs
models [BRANDING] Use forgejo binary name 2023-12-11 15:42:59 +01:00
modules [BRANDING] parse FORGEJO__* in the container environment 2023-12-11 15:42:59 +01:00
options
public [BRANDING] Custom loading animation for Forgejo 2023-12-11 15:42:58 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2023-12-11 14:48:34 +01:00
routers [BRANDING] Use forgejo binary name 2023-12-11 15:42:59 +01:00
services [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-12-11 15:42:59 +01:00
snap
templates [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-12-11 15:42:59 +01:00
tests [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-12-11 15:42:59 +01:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-12-11 15:42:58 +01:00
.air.toml
.changelog.yml
.deadcode-out [DEADCODE] update deadcode-out 2023-12-11 14:51:07 +01:00
.dockerignore
.editorconfig
.eslintrc.yaml
.gitattributes [META] Use correct language for .tmpl 2023-12-11 14:48:36 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2023-12-11 14:51:07 +01:00
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
build.go
CHANGELOG.md
CODEOWNERS [META] Add CODEOWNERS files 2023-12-11 14:48:36 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-12-11 14:33:55 +01:00
DCO
Dockerfile [CI] Forgejo Actions based release process 2023-12-11 13:55:27 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2023-12-11 13:55:27 +01:00
go.mod
go.sum
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-12-11 14:48:35 +01:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-12-11 15:42:59 +01:00
MAINTAINERS
Makefile [BRANDING] add forgejo target to Makefile 2023-12-11 15:42:59 +01:00
package-lock.json
package.json
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-12-11 15:42:58 +01:00
README.md [BRANDING] add Forgejo logo 2023-12-11 15:42:58 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-12-11 14:48:34 +01:00
vitest.config.js
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-12-11 14:48:35 +01:00

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.