cb87f29b76
Why: * We are using self-signed ssl certificates for internal services, which results in failures when gitea tries to communicate through webhooks with these. We would like to enable gitea to be able to use these certificates without having to build custom docker images. How * We add the internal certificates to /usr/local/share/ca-certificates on the host * We read-only mount /usr/local/share/ca-certificates from the host to /usr/local/share/ca-certificates in the container * We do a update-ca-certificates in the alpine container before starting gitea This should have no consequence for users that do not have the need to handle self-signed certificates, as update-ca-certificates should be idempotent. |
||
|---|---|---|
| .github | ||
| assets | ||
| cmd | ||
| contrib | ||
| custom/conf | ||
| docker | ||
| docs | ||
| integrations | ||
| models | ||
| modules | ||
| options | ||
| public | ||
| routers | ||
| scripts | ||
| templates | ||
| vendor | ||
| .changelog.yml | ||
| .drone.yml | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .lgtm | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| LICENSE | ||
| main.go | ||
| MAINTAINERS | ||
| Makefile | ||
| package.json | ||
| README_ZH.md | ||
| README.md | ||
Gitea - Git with a cup of tea
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Purpose
The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service. Using Go, this can be done with an independent binary distribution across all platforms which Go supports, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. Want to try it before doing anything else? Do it with the online demo! This project has been forked from Gogs since 2016.11 but changed a lot.
Building
From the root of the source tree, run:
make generate all
More info: https://docs.gitea.io/en-us/install-from-source/
Using
./gitea web
NOTE: If you're interested in using our APIs, we have experimental support with documentation.
Contributing
Expected workflow is: Fork -> Patch -> Push -> Pull Request
NOTES:
- YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
- If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!
Further information
For more information and instructions about how to install Gitea, please look at our documentation. If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server, Matrix room, or forum!
Authors
License
This project is licensed under the MIT License. See the LICENSE file for the full license text.