gitea

Дерево: faa28b5a44

Автор	SHA1	Повідомлення	Дата
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>	11 місяці тому
silverwind	d86f878b3e	optimize all images in public/img (#6427) Fixes: https://github.com/go-gitea/gitea/pull/6357	5 роки тому
unclejack	8bc431952f	public/img: reduce the size of PNG images (#734) Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com>	7 роки тому
Unknwon	4217c2333c	new create webhook UI	8 роки тому

1 Коміти (faa28b5a44912f1c63afddab9396bae9e6fe061c)