4 Commits (2b4d43dd4d7388ff73e99c143008ad4663142e61)

Author	SHA1	Message	Date
Lunny Xiao	1a9821f57a	Move issues related files into models/issues (#19931) ... * Move access and repo permission to models/perm/access * fix test * fix git test * Move functions sequence * Some improvements per @KN4CK3R and @delvh * Move issues related code to models/issues * Move some issues related sub package * Merge * Fix test * Fix test * Fix test * Fix test * Rename some files	2 years ago
zeripath	d494cc3356	Fix nodeinfo caching and prevent NPE if cache non-existent (#19721) ... Extract from #19703 Signed-off-by: Andrew Thornton <art27@cantab.net>	3 years ago
6543	e2a3f3d259	Federation: return useful statistic information for nodeinfo (#19561) ... Add statistic information for total user count, active user count, issue count and comment count for `/nodeinfo`	3 years ago
techknowlogick	babab0bf5e	Add nodeinfo endpoint for federation purposes (#16953) ... Nodeinfo is a way to expose certain metadata about a server for use of discovery regarding functionality of its federation capabilities. Two endpoints are required: 1. `/.well-known/nodeinfo` which informs client where it can find the location of the location of its metadata (including which version of the schema is used) 2. the endpoint which exposes the metadata in json format according to schema. Notes: * `openRegistrations` is a required field, but I propose to set to false as default in case someone writes a crawler to discover "open" gitea instances * to limit data leakage I also propose to not include the `usage` field (note it is required so it should be included, but left as empty). More info: https://github.com/jhass/nodeinfo https://github.com/jhass/nodeinfo/tree/main/schemas/2.1 http://nodeinfo.diaspora.software/protocol.html	3 years ago