2 commits

Author	SHA1	Message	Date
Caesar Schinas	66a6726a28	[BRANDING] add Forgejo logo ... (cherry picked from commit f42622c7d5) (cherry picked from commit a39e7f2a79) (cherry picked from commit afa2a31bb9) (cherry picked from commit 276e8856e5) (cherry picked from commit 68e3bd469f) (cherry picked from commit af124b9ccb) (cherry picked from commit b89ab4874d) (cherry picked from commit 0f2a2f0d0f) (cherry picked from commit 80999363c7) (cherry picked from commit f8880b5463) (cherry picked from commit 5f4cf4f6e1) (cherry picked from commit b38e26bc1a) (cherry picked from commit d839e00332) (cherry picked from commit 32ffe2e4f1) (cherry picked from commit f1fd0504ad) (cherry picked from commit 6d77ea4d60) (cherry picked from commit 61a0a4a276) (cherry picked from commit a90b4126fd) (cherry picked from commit 9a20538fb4) (cherry picked from commit ce0fc02f0f) (cherry picked from commit 541f7cb026) (cherry picked from commit d6d0c2ab78) (cherry picked from commit 2c28f5ad24) (cherry picked from commit 9571bddb33) (cherry picked from commit c83ba08d01) (cherry picked from commit 30e7d567ed) (cherry picked from commit a8b8c3eba7) (cherry picked from commit 8e053e1ade) (cherry picked from commit 9e3b0f7520) (cherry picked from commit 2343b9bd09) (cherry picked from commit 56572d4156) (cherry picked from commit 9b09eda168) (cherry picked from commit 86a8b7b490) (cherry picked from commit 99a550c0e3) (cherry picked from commit d68422d187) (cherry picked from commit 4eb58c117d) (cherry picked from commit 78142114b6) (cherry picked from commit 461c883396) (cherry picked from commit e1f97e5307)	2023-11-13 13:58:17 +01:00
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

Renamed from public/img/logo.svg (Browse further)