summaryrefslogtreecommitdiff
path: root/lib/gitlab/favicon.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-071-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-131-0/+2
|
* fix(favicon): get favicon_path, so it works also with uploads object storeRoger Meier2019-06-141-6/+2
|
* Refactor Gitlab::Favicon for EEYorick Peterse2019-03-121-1/+7
| | | | | This moves the development favicon name in Gitlab::Favicon to a separate method, allowing EE to redefine it to return a custom favicon.
* Enable frozen string for lib/gitlab/*.rbgfyoung2018-10-221-0/+2
|
* Use `Gitlab::SafeRequestStore` in more placesMichael Kozono2018-09-241-1/+1
| | | | | | Even if it doesn’t save lines of code, since people will tend to use code they’ve seen. And `SafeRequestStore` is safer since you don’t have to remember to check `RequestStore.active?`.
* Read asset host from ActionController::Base instead of application configDouwe Maan2018-06-291-1/+2
|
* Fix: Serve favicon image always from the main GitLab domain to avoid issues ↵Alexis Reigel2018-06-201-5/+15
| | | | with CORS
* Remove FaviconUploader favicon_main versiondm-remove-favicon-main-versionDouwe Maan2018-06-151-1/+1
| | | | See https://gitlab.com/gitlab-org/gitlab-ce/issues/47677 for more information
* dry up asset path helper callsAlexis Reigel2018-06-051-3/+10
|
* the '?' favicon hack doesn't seem to be requiredAlexis Reigel2018-06-051-8/+1
| | | | probably due to recent changes in `UploadsController`.
* remove favicon preview on appearance pageAlexis Reigel2018-06-051-6/+0
|
* remove all .ico favicon variations, use png alwaysAlexis Reigel2018-06-051-5/+4
| | | | | the ci status icons are generated client side, wo we don't need the static files anymore.
* create favicon overlay on the clientAlexis Reigel2018-06-051-12/+21
| | | | | | | | | | | | | the initial reason for this change was that graphicsmagick does not support writing to ico files. this fact lead to a chain of changes: 1. use png instead of ico (browser support is good enough) 2. render the overlays on the client using the canvas API. this way we only need to store the original favion and generate the overlay versions dynamically. this change also enables (next step) to simplify the handling of the stock favicons as well, as we don't need to generate all the versions upfront.
* call Gitlab::Favicon.status in serializerAlexis Reigel2018-06-051-7/+10
| | | | | | | | | this ways we can keep the `lib/gitlab/ci/status/*` classes to return the bare favicon name as it was before. also the favicon uploader versions are now have the same names as the stock favicons (+ `favicon_` prefix), which makes working with the status names easier.
* add request store caching to faviconAlexis Reigel2018-06-051-1/+1
|
* Add a '?' to the custom favicon's urlsAlexis Reigel2018-06-051-2/+9
| | | | | | | | Without the '?' at the end of the favicon url the custom favicon (i.e. the favicons that are served through `UploadController`) are not shown in the browser. It may have something to do with how `#send_file` / `#send_data` set http headers. When serving the same icon file from the public directory everything is fine.
* use custom favicon for ci build status faviconsAlexis Reigel2018-06-051-3/+15
|
* extract favicon logic to lib classAlexis Reigel2018-06-051-0/+23