5 Commits (65b9ffe3c081b54234306b2d6231569bff3ce02d)

Author	SHA1	Message	Date
Lunny Xiao	6624f257d3	Docker Tag Information in Docs (#29047) (#29362) ... Backport #29047 Add more details for the docker tag when using container registry. Co-authored-by: wienans <40465543+wienans@users.noreply.github.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>	1 year ago
CEnnis91	315155fab0	Fix incorrect link to swift doc and swift package-registry login command (#29096) (#29103)	1 year ago
Giteabot	373e78895e	switch destination directory for apt signing keys (#28639) (#28642) ... Backport #28639 by @denyskon According to [Debian docs](https://wiki.debian.org/DebianRepository/UseThirdParty): > The certificate MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add. > ... > If future updates to the certificate will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into /usr/share/keyrings using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into /etc/apt/keyrings instead. > ... > A sources.list entry SHOULD have the signed-by option set. Co-authored-by: Denys Konovalov <kontakt@denyskon.de>	1 year ago
merlleu	e6a059a3d0	add sparse url in cargo package guide (#26937) ... Hello, The current package guide for cargo gives you only the git index, with the HTTP Index stabilized being used as default for crates.io and being better for most use-cases. However, it's not documented that gitea supports the sparse spec, and it does not require the _crates-index git repo for the sparse api. I personally think we should push users to use the sparse instead of the git repository. (Even let users disable crates-index repos if they only want to use sparse)	1 year ago
John Olheiser	bd4c7ce578	Docusaurus-ify (#26051) ... This PR cleans up the docs in a way to make them simpler to ingest by our [docs repo](https://gitea.com/gitea/gitea-docusaurus). 1. It includes all of the sed invocations our ingestion did, removing the need to do it at build time. 2. It replaces the shortcode variable replacement method with `@variable@` style, simply for easier sed invocations when required. 3. It removes unused files and moves the docs up a level as cleanup. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>	2 years ago