Go to file
Earl Warren 62cae8cc6a
[BRANDING] parse FORGEJO__* in the container environment
Add the FORGEJO__ prefix as equivalent to GITEA__ when interpreted by
environment-to-ini. It is used when running the Forgejo container like
so:

  docker run --name forgejo -e FORGEJO__security__INSTALL_LOCK=true \
             -d codeberg.org/forgejo/forgejo:1.18

Signed-off-by: Earl Warren <contact@earl-warren.org>
(cherry picked from commit 6cd61e2ab7)
2023-02-20 12:02:25 +01:00
.gitea [WORKFLOW] issues & pr templates 2023-02-20 10:09:56 +01:00
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-02-20 12:02:25 +01:00
assets [BRANDING] add Forgejo logo 2023-02-20 11:26:44 +01:00
build Consume hcaptcha and pwn deps (#22610) 2023-01-29 09:49:51 -06:00
cmd [BRANDING] Rename usage of Gitea in user-visible places 2023-02-20 11:47:44 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-02-20 12:02:25 +01:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-02-20 10:09:49 +01:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-02-20 11:37:18 +01:00
docker [BRANDING] container images: set APP_NAME 2023-02-20 11:41:27 +01:00
docs Add some guidelines for refactoring (#22880) 2023-02-19 21:25:23 +08:00
models Make CI use a dummy password hasher for all tests (#22983) 2023-02-20 13:20:30 +08:00
modules [BRANDING] Rebrand default meta tags 2023-02-20 11:47:42 +01:00
options Scoped labels (#22585) 2023-02-18 21:17:39 +02:00
public [BRANDING] Custom loading animation for Forgejo 2023-02-20 11:41:25 +01:00
releases [DOCS] RELEASE-NOTES.md 2023-02-20 10:09:57 +01:00
routers [BRANDING] Rebrand default config settings for new installs (#140) 2023-02-20 11:37:18 +01:00
services Refactor the setting to make unit test easier (#22405) 2023-02-20 00:12:01 +08:00
snap Remove unnecessary whitespace in snapcraft.yaml (#22090) 2022-12-10 08:31:16 -06:00
templates [BRANDING] Replace branding in Swagger 2023-02-20 12:02:13 +01:00
tests [API] Forgejo API /api/forgejo/v1 2023-02-20 10:10:06 +01:00
tools Move fuzz tests into tests/fuzz (#22376) 2023-01-09 15:30:14 +08:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-02-20 11:44:16 +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 Adjust manifest to prevent tagging latest on rcs (#22811) 2023-02-19 09:24:08 -05: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-02-20 09:10:03 +01:00
.gitpod.yml Split default gitpod view to include all tasks (#22555) 2023-01-20 13:46:33 -06:00
.golangci.yml Fix .golangci.yml (#22868) 2023-02-11 21:44:53 +00:00
.ignore
.lgtm
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
BSDmakefile
build.go
CHANGELOG.md Frontport 1.18.2 and 1.18.3 Changelogs (#22580) 2023-01-23 09:36:00 -06:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-02-20 10:09:49 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] implementation: forgejo container images 2023-02-20 09:10:54 +01:00
Dockerfile.rootless [CI] implementation: forgejo container images 2023-02-20 09:10:54 +01:00
go.mod Use import of OCI structs (#22765) 2023-02-06 10:07:09 +00:00
go.sum Use import of OCI structs (#22765) 2023-02-06 10:07:09 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-02-20 10:10:06 +01:00
main.go Support asciicast files as new markup (#22448) 2023-01-18 08:46:58 +08:00
MAINTAINERS Remove thehowl from maintainers (#22917) 2023-02-15 08:35:46 -06:00
Makefile [BRANDING] Replace branding in Swagger 2023-02-20 12:02:13 +01:00
package-lock.json Implement actions (#21937) 2023-01-31 09:45:19 +08:00
package.json Implement actions (#21937) 2023-01-31 09:45:19 +08:00
playwright.config.js
README.md [BRANDING] add Forgejo logo 2023-02-20 11:26:44 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-02-20 10:09:57 +01:00
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-02-20 10:10:06 +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. 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.