Git with a cup of tea, painless self-hosted git service Mirror for internal git.with.parts use https://git.with.parts

Alexander Scheel 1bf9e44bda Fix sanitizer config - multiple rules (#11133 ) In #9888, it was reported that my earlier pull request #9075 didn't quite function as expected. I was quite hopeful the `ValuesWithShadow()` worked as expected (and, I thought my testing showed it did) but I guess not. @zeripath proposed an alternative syntax which I like: ```ini [markup.sanitizer.1] ELEMENT=a ALLOW_ATTR=target REGEXP=something [markup.sanitizer.2] ELEMENT=a ALLOW_ATTR=target REGEXP=something ``` This was quite easy to adopt into the existing code. I've done so in a semi-backwards-compatible manner: - The value from `.Value()` is used for each element. - We parse `[markup.sanitizer]` and all `[markup.sanitizer.*]` sections and add them as rules. This means that existing configs will load one rule (not all rules). It also means people can use string identifiers (`[markup.sanitiser.KaTeX]`) if they prefer, instead of numbered ones. Co-authored-by: Andrew Thornton <art27@cantab.net> Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>		5 years ago
.github	Improve stale message (#9920 )	5 years ago
assets	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
build	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
cmd	Return error for authorized_keys and mergebase problems (#10990 )	5 years ago
contrib	Add gitea-vet (#10948 )	5 years ago
custom/conf	Fix sanitizer config - multiple rules (#11133 )	5 years ago
docker	Fix latest docker image haven't include static files. (#9252 )	5 years ago
docs	Fix sanitizer config - multiple rules (#11133 )	5 years ago
integrations	Make the PushCreate test declarative (#11229 )	5 years ago
models	BugFix: updateLabel can updated not allowed fields #11242 (#11242 )	5 years ago
modules	Fix sanitizer config - multiple rules (#11133 )	5 years ago
options	[skip ci] Updated translations via Crowdin	5 years ago
public	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
routers	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
services	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
snap	Remove explicit 'generate' calls, fix release task (#9288 )	5 years ago
templates	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
vendor	Use markdown frontmatter to provide Table of contents, language and frontmatter rendering (#11047 )	5 years ago
web_src	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
.changelog.yml	Changelog 1.11.0 (#10204 ) (#10211 )	5 years ago
.drone.yml	Skip frontend build where unnecessary (#11159 )	5 years ago
.editorconfig	move CSS build to webpack (#9983 )	5 years ago
.eslintrc	Support unicode emojis and remove emojify.js (#11032 )	5 years ago
.gitattributes	Rename scripts to build and add revive command as a new build tool command (#10942 )	5 years ago
.gitignore	Use /tmp for test repositories (#11126 )	5 years ago
.golangci.yml	Improve push update options (#10105 )	5 years ago
.ignore	remove promise-polyfill (#9812 )	5 years ago
.lgtm	refactor: ignore LGTM from author of pull request. (#3283 )	7 years ago
.npmrc	add package-lock=true in .npmrc (#9736 )	5 years ago
.revive.toml	refactor: replace lint to revive (#5422 )	6 years ago
.stylelintrc	Disallow leading zeroes in Less (#10407 )	5 years ago
BSDmakefile	Add BSDmakefile to prevent errors when `make` is called under FreeBSD (#4446 )	6 years ago
CHANGELOG.md	Changelog v1.11.4 (#10916 ) (#10917 )	5 years ago
CONTRIBUTING.md	move CSS build to webpack (#9983 )	5 years ago
DCO	follow the advisor: add DCO and some improvements	8 years ago
Dockerfile	go 1.14 (#10467 )	5 years ago
LICENSE	Fix typo	8 years ago
MAINTAINERS	Update Owners for upcoming year (#9290 )	5 years ago
Makefile	Use /tmp for test repositories (#11126 )	5 years ago
README.md	go 1.14 (#10467 )	5 years ago
README_ZH.md	update discord link (#10455 )	5 years ago
build.go	Add gitea-vet (#10948 )	5 years ago
go.mod	Use markdown frontmatter to provide Table of contents, language and frontmatter rendering (#11047 )	5 years ago
go.sum	Vendor Update: go-gitlab v0.22.1 -> v0.31.0 (#11136 )	5 years ago
main.go	Prevent support libraries from compiling into Gitea (#10964 )	5 years ago
package-lock.json	Update JS dependencies, highlight.js 10.0.0 (#11195 )	5 years ago
package.json	Update JS dependencies, highlight.js 10.0.0 (#11195 )	5 years ago
semantic.json	Update JS dependencies (#10450 )	5 years ago
webpack.config.js	Move syntax highlighting to web worker (#11017 )	5 years ago

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:

TAGS="bindata" make build

or if sqlite support is required:

TAGS="bindata sqlite sqlite_unlock_notify" make build

The build target is split into two sub-targets:

make backend which requires Go 1.12 or greater.
make frontend which requires Node.js 10 or greater.

If pre-built frontend files are present it is possible to only build the backend:

	TAGS="bindata" make backend

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, or forum!