gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move public asset files to the proper directory (#25907)	wxiaoguang	2023-07-18	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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>
*	Clean up SVG (#13680)	techknowlogick	2020-12-17	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Clean up SVG * update per feedback * fix css style * Delete gitea.png * no new line at end of file * fix newline? Co-authored-by: 6543 <6543@obermui.de>
*	Rework 'make generate-images' (#12316)	silverwind	2020-07-26	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Rework 'make generate-images' - Remove external dependencies and replace it with a node script that does does the same. - Move detail removal from gitea-sm.png to favicon.png - Remove favicon.ico and its generation, it is unused and we already serve favicon.png in its place. Fixes: https://github.com/go-gitea/gitea/issues/12314 * use proper centering value for preserveAspectRatio * fix lint * use fabric * better linting fix * fix typo * mention detail-remove class in docs
*	optimize all images in public/img (#6427)	silverwind	2019-03-25	1	-0/+0
\| \| \|	Fixes: https://github.com/go-gitea/gitea/pull/6357
*	Add task to generate images from SVG and change to new logo (#2194)	Lauris BH	2017-07-28	1	-0/+0
\| \| \| \| \| \|	* Add makefile task to generate images from SVG and change to new logo * use absolute path on generate-images
*	Optimize png images via Google zopflipng [ci skip] (#1639)	Peter Dave Hello	2017-04-30	1	-0/+0
\|
*	first batch of Readme updates (#65)	Rachid Zarouali	2016-11-10	1	-0/+0
\|
*	Use a gopher as default avatar (rather than the gravatar logo) (#3208)	Sandro Santilli	2016-06-27	1	-0/+0
	Also changes the avatar from a jpeg to a png, to allow for transparent background. The indexed png is also smaller in size. Note that at the moment the default avatar is only used when the user requested a custom avatar and the custom avatar file is not found (should never happen). In the future the default avatar could be used as a default return when by-mail avatar lookups fail too (both gravatar and libravatar support passing a default)