2 commits

Author	SHA1	Message	Date
Caesar Schinas	edc5c3c304	[BRANDING] Add forgejo emoji ... (cherry picked from commit ade55ad308) (cherry picked from commit 107f726618) (cherry picked from commit f29cf9cfc1) (cherry picked from commit 0761a41eee) (cherry picked from commit 2b1fd9565f) (cherry picked from commit 6a7c82f13b) (cherry picked from commit 4a56d40494) (cherry picked from commit b48e3e896d) (cherry picked from commit bde83340cb) (cherry picked from commit 74e0603d6b) (cherry picked from commit 84bd1ddc08) (cherry picked from commit 62d9acde2a) (cherry picked from commit 5b84a90913) (cherry picked from commit 5362f7d053) (cherry picked from commit 65ad7d1bd9) (cherry picked from commit 6e42d545a9) (cherry picked from commit 24d3bb33e2) (cherry picked from commit 704935cadd) (cherry picked from commit 5d9fc59e17) (cherry picked from commit 4c95df3f86) (cherry picked from commit 1ac704762a) (cherry picked from commit 0da9fb1318) (cherry picked from commit bc2de51eef) (cherry picked from commit ea897a20b9) (cherry picked from commit 66f3f9c6ef)	2023-08-14 10:58:31 +02: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