wxiaoguang faa28b5a44 Move public asset files to the proper directory (#25907) ... Move `public/*` to `public/assets/*` Some old PRs (like #15219) introduced inconsistent directory system. For example: why the local directory "public" is accessed by `http://site/assets`? How to serve the ".well-known" files properly in the public directory? For convention rules, the "public" directory is widely used for the website's root directory. It shouldn't be an exception for Gitea. So, this PR makes the things consistent: * `http://site/assets/foo` means `{CustomPath}/public/assets/foo`. * `{CustomPath}/public/.well-known` and `{CustomPath}/public/robots.txt` can be used in the future. This PR is also a prerequisite for a clear solution for: * #21942 * #25892 * discourse.gitea.io: [.well-known path serving custom files behind proxy?](https://discourse.gitea.io/t/well-known-path-serving-custom-files-behind-proxy/5445/1) This PR is breaking for users who have custom "public" files (CSS/JS). After getting approvals, I will update the documents. ---- ## ⚠️ BREAKING ⚠️ If you have files in your "custom/public/" folder, please move them to "custom/public/assets/". --------- Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Giteabot <teabot@gitea.io>		2023-07-18 18:06:43 +02:00
..
emoji	Move public asset files to the proper directory (#25907)	2023-07-18 18:06:43 +02:00
svg
404.png
500.png
apple-touch-icon.png
avatar_default.png
checkmark.png
dingtalk.ico
discord.png
failed.png
favicon.png
favicon.svg
feishu.png	Move public asset files to the proper directory (#25907)	2023-07-18 18:06:43 +02:00
gitea.svg
gogs.ico	Move public asset files to the proper directory (#25907)	2023-07-18 18:06:43 +02:00
loading.png
logo.png	Move public asset files to the proper directory (#25907)	2023-07-18 18:06:43 +02:00
logo.svg
msteams.png
openid-16x16.png
packagist.png
repo_default.png
slack.png
telegram.png
wechatwork.png