Go to file
Loïc Dachary af8864373a
[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)
2023-03-18 11:10:24 +01:00
.gitea [WORKFLOW] issues & pr templates 2023-03-18 09:20:23 +01:00
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-03-18 11:10:23 +01:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-03-18 09:20:01 +01:00
assets [BRANDING] add Forgejo logo 2023-03-18 10:28:31 +01:00
build Improve sed detection in update-locales.sh (#23254) 2023-03-04 14:29:28 +00:00
cmd [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-03-18 11:10:23 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-03-18 11:10:23 +01:00
custom/conf [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-03-18 11:10:23 +01:00
docker [BRANDING] container images: set APP_NAME 2023-03-18 10:28:32 +01:00
docs [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-03-18 11:10:23 +01:00
models [BRANDING] reserve forgejo-actions username 2023-03-18 11:10:23 +01:00
modules [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-03-18 11:10:24 +01:00
options [skip ci] Updated translations via Crowdin 2023-03-18 00:16:14 +00:00
public [BRANDING] Custom loading animation for Forgejo 2023-03-18 10:28:32 +01:00
releases [DOCS] RELEASE-NOTES: 1.19.0 2023-03-18 09:20:24 +01:00
routers [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-03-18 11:10:24 +01:00
services [BRANDING] [v1.20] define the forgejo webhook type 2023-03-18 11:10:23 +01:00
snap Remove unnecessary whitespace in snapcraft.yaml (#22090) 2022-12-10 08:31:16 -06:00
templates [BRANDING] [v1.20] define the forgejo webhook type 2023-03-18 11:10:23 +01:00
tests [BRANDING] Update nodeinfo branding 2023-03-18 11:10:23 +01:00
tools Move fuzz tests into tests/fuzz (#22376) 2023-01-09 15:30:14 +08:00
web_src [BRANDING] [v1.20] Add Forgejo light, dark, and auto themes 2023-03-18 11:10:20 +01:00
.air.toml Add more test directory to exclude dir of air, remove watching templates from air include dir because gitea has internal mechanism (#22246) 2022-12-27 14:00:34 +08:00
.changelog.yml
.dockerignore
.drone.yml Update JS dependencies, Require Node.js 16 (#23528) 2023-03-17 01:45:45 -04:00
.editorconfig
.eslintrc.yaml Refactor hiding-methods, remove jQuery show/hide, remove `.hide` class, remove inline style=display:none (#22950) 2023-02-19 12:06:14 +08:00
.gitattributes
.gitignore [CI] implementation: Woodpecker based CI 2023-03-18 08:23:50 +01:00
.gitpod.yml Write Gitpod `app.ini` only once (#23192) 2023-02-28 23:30:43 +08:00
.golangci.yml Fix .golangci.yml (#22868) 2023-02-11 21:44:53 +00:00
.ignore
.lgtm
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml Replace Less with CSS (#23481) 2023-03-14 22:20:19 -04:00
BSDmakefile
CHANGELOG.md Changelog 1.18.5 (#23045) (#23049) 2023-02-21 13:36:19 -06: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-03-18 09:20:01 +01: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-03-18 11:10:24 +01:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-03-18 11:10:24 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-03-18 09:20:23 +01:00
MAINTAINERS Remove xin-u from maintainers (#23170) 2023-02-27 03:20:57 -05:00
Makefile [BRANDING] Replace branding in Swagger 2023-03-18 11:10:23 +01:00
README.md [BRANDING] add Forgejo logo 2023-03-18 10:28:31 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES: 1.19.0 2023-03-18 09:20:24 +01:00
build.go
go.mod Update act (#23512) 2023-03-16 18:09:11 +08:00
go.sum Update act (#23512) 2023-03-16 18:09:11 +08:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-03-18 11:10:24 +01:00
package-lock.json Remove worker-loader (#23548) 2023-03-18 00:36:32 -04:00
package.json Remove worker-loader (#23548) 2023-03-18 00:36:32 -04:00
playwright.config.js
vitest.config.js Update JS dependencies and eslint (#22190) 2022-12-20 17:15:47 -05:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-03-18 09:20:23 +01:00

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. Interested? Read more

Learn more

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.