- Go 77.3%
- go-html-template 10.8%
- Roff 4.3%
- JavaScript 2.7%
- CSS 2.1%
- Other 2.6%
Gusted
f64809496a
I'm not exactly sure if this is the correct fix or if this fixes the issue, but at some point `bad driver` errors is being returned specifically for debian repository files. This brings the transaction for each package rule, where a transaction makes more sense to happen. Reported by at least one other Forgejo instance, should be upstreamed when confirmed to fix the issue. |
||
|---|---|---|
| .devcontainer | ||
| .forgejo | ||
| assets | ||
| build | ||
| cmd | ||
| contrib | ||
| custom/conf | ||
| docker | ||
| models | ||
| modules | ||
| options | ||
| public | ||
| release-notes | ||
| release-notes-published | ||
| releases/images | ||
| routers | ||
| services | ||
| templates | ||
| tests | ||
| tools | ||
| web_src | ||
| .air.toml | ||
| .deadcode-out | ||
| .dockerignore | ||
| .editorconfig | ||
| .envrc.example | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .gitpod.yml | ||
| .golangci.yml | ||
| .ignore | ||
| .mailmap | ||
| .markdownlint.yaml | ||
| .node-version | ||
| .npmrc | ||
| .release-notes-assistant.yaml | ||
| .spectral.yaml | ||
| .yamllint.yaml | ||
| BSDmakefile | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| Dockerfile.rootless | ||
| eslint.config.mjs | ||
| flake.lock | ||
| flake.nix | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| manifest.scm | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| README.md | ||
| release-notes-assistant.sh | ||
| RELEASE-NOTES.md | ||
| renovate.json | ||
| shell.nix | ||
| stylelint.config.js | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vitest.config.ts | ||
| webpack.config.js | ||
Forgejo (Codeberg)
Codeberg's fork of Forgejo, a self-hosted lightweight software forge.
Some changes made to Forgejo's source code are:
- Codeberg-specific themes
- Codeberg's custom landing page
- Codeberg's custom footer
- Various optimizations necessary for running a large instance
- Dirty hacks that we needed to deploy as soon as possible
Some of our patches may be helpful if you wish to operate a large Forgejo instance. However, this repository as a whole contains a custom version of Forgejo that is explicitly not intended for private use.
Codeberg and Forgejo work together, but, as projects, they remain separate. For more information about Forgejo and its relationship with Codeberg, take a look at Forgejo's FAQ.
Reporting Issues
If you wish to report an issue for the changes that Codeberg has made or are not sure where you should open an issue for a service hosted by Codeberg, please create an issue on Codeberg/Community.
Additionally, Forgejo maintains its own Issue Tracker for bug reports and feature requests.
Hosting
If you wish to host Forgejo on your own, please visit forgejo.org.
You can find some other repositories that help us operate codeberg.org in the Codeberg-Infrastructure organisation.
Our instance's Forgejo configuration files can be found here: Codeberg-Infrastructure/build-deploy-forgejo
Tip
The configuration files include the settings required to enable the Codeberg-specific Forgejo themes, i.e.
codeberg-auto,codeberg-light,codeberg-darkin your local Forgejo instance.
Contributing
We follow the upstream Forgejo tree and most of the decisions that they make for everyone else.
If you want to send a patch to codeberg.org, the best way to do that is probably sending a patch to Forgejo.
Branding
Codeberg has a set of design-related guidelines, which can be found here.
Reporting Vulnerabilities
See security.txt