Beyond coding. We forge.
Find a file
Loïc Dachary 0fb9ed7e0e
[BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR}
FORGEJO_* environment variables are set to the corresponding GITEA_*
variable when the cli starts. This approach is intended to minimize
the conflicts on rebase. All occurences of GITEA_* are left untouched
in the codebase and they are only changed to FORGEJO_* if exposed to
the user.

(cherry picked from commit e466f9d10e)
(cherry picked from commit e33e95931b)
(cherry picked from commit 2cfc6519b7)
(cherry picked from commit af8864373a)
(cherry picked from commit a0550ff339)
(cherry picked from commit 24dc0a5191)
(cherry picked from commit e255eea2b4)
(cherry picked from commit 0c4f5afa7a)
(cherry picked from commit 42fce708d0)
(cherry picked from commit e7278c3c22)
2023-05-16 11:17:53 +02:00
.gitea [WORKFLOW] issues & pr templates 2023-05-16 10:03:04 +02:00
.github/workflows delete Gitea specific files that need rewriting for Forgejo 2023-05-16 10:03:04 +02:00
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-05-16 11:17:52 +02:00
assets [BRANDING] add Forgejo logo 2023-05-16 11:10:58 +02:00
build Replace placeholders in licenses (#24354) 2023-05-05 13:46:17 +00:00
cmd [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-05-16 11:16:02 +02:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-05-16 11:17:52 +02:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-05-16 10:03:04 +02:00
custom/conf [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-05-16 11:17:53 +02:00
docker [BRANDING] container images: set APP_NAME 2023-05-16 11:16:02 +02:00
docs [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-05-16 11:17:53 +02:00
models [BRANDING] reserve forgejo-actions username 2023-05-16 11:17:53 +02:00
modules [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-05-16 11:17:53 +02:00
options [skip ci] Updated translations via Crowdin 2023-05-16 00:23:56 +00:00
public [BRANDING] Custom loading animation for Forgejo 2023-05-16 11:16:02 +02:00
releases [DOCS] RELEASE-NOTES.md 2023-05-16 10:03:04 +02:00
routers [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-05-16 11:17:53 +02:00
services [BRANDING] define the forgejo webhook type 2023-05-16 11:17:53 +02:00
snap Remove unnecessary whitespace in snapcraft.yaml (#22090) 2022-12-10 08:31:16 -06:00
templates [BRANDING] define the forgejo webhook type 2023-05-16 11:17:53 +02:00
tests [BRANDING] Update nodeinfo branding 2023-05-16 11:17:53 +02:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-05-16 11:16:02 +02:00
.air.toml Set stop_on_error (#24453) 2023-04-30 18:31:16 -04:00
.changelog.yml Changelog for v1.15.0-rc1 (#16422) 2021-07-15 11:47:57 -04:00
.dockerignore Add .dockerignore (#21753) 2022-11-10 04:04:09 +01:00
.drone.yml Upgrade to Node 20 on CI, enable actions cancellation (#24524) 2023-05-04 22:21:48 +00:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Switch to @eslint-community/eslint-comments (#24736) 2023-05-15 17:29:23 +00:00
.gitattributes Mark /templates/swagger/v1_json.tmpl as generated file (#24306) 2023-04-24 13:18:24 -04:00
.gitignore [CI] implementation: Woodpecker based CI 2023-05-16 07:33:34 +02:00
.gitpod.yml Use official Vue extension in Gitpod (#24609) 2023-05-09 18:03:50 +00:00
.golangci.yml Enable forbidigo linter (#24278) 2023-04-24 05:50:58 -04:00
.ignore Add some .ignore entries (#18296) 2022-01-16 17:26:15 +00:00
.markdownlint.yaml Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml Add spectral linter for Swagger (#20321) 2022-07-11 18:07:16 -05:00
.stylelintrc.yaml Reorganize CSS files (#24739) 2023-05-16 00:13:30 -04:00
BSDmakefile update BSDmakefile to latest version from upstream (#24063) 2023-04-11 23:42:22 -04:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Changelog for 1.19.3 (#24495) (#24506) 2023-05-03 22:05:47 -04:00
CODE_OF_CONDUCT.md Add Gitea Community Code of Conduct (#23188) 2023-03-09 10:49:34 +08:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-05-16 10:03:04 +02:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [BRANDING] symlink gitea to forgejo in docker containers 2023-05-16 11:17:53 +02:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-05-16 11:17:53 +02:00
go.mod Add RPM registry (#23380) 2023-05-05 20:33:37 +00:00
go.sum Add RPM registry (#23380) 2023-05-05 20:33:37 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-05-16 10:03:04 +02:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-05-16 11:17:53 +02:00
MAINTAINERS Apply to become maintainer (#24254) 2023-04-21 21:23:16 +08:00
Makefile [BRANDING] Replace branding in Swagger 2023-05-16 11:17:47 +02:00
package-lock.json Bump vm2 from 3.9.17 to 3.9.18 (#24742) 2023-05-15 23:55:56 +02:00
package.json Switch to @eslint-community/eslint-comments (#24736) 2023-05-15 17:29:23 +00:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
README.md [BRANDING] add Forgejo logo 2023-05-16 11:10:58 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-05-16 10:03:04 +02:00
vitest.config.js Update JS dependencies (#24218) 2023-04-19 22:36:41 -04:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-05-16 10:03:04 +02: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.