Feature Request - static URLs for assets
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
Some customers would benefit from having URLs for static assets, such as CSS and Javascript files. Currently the way we implement this is to minify the content and that changes the URL slightly.
What this looks like is as follows:
- Given the file https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/editor/schema/ci.json and the path ("app/assets/javacripts/editor/schema/ci.json")
- After minifying it becomes "/assets/webpack/ci.27b78ab0.json"
The idea for some customers is to have some of these files be static, apropos to a symlink to it, for example
-
/assets/webpack/ci.27b78ab0.jsonsymlink to./webpack/ci.jsonfile
A workaround for the above would be to reference the URL via the one stored in the repository, for example - https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/editor/schema/ci.json
However, for offline environments they essentially need to search the directories to find the file in order to reference it:
/opt/gitlab/embedded/service/gitlab-rails/public/assets# rg -i 'built-in solution' .
./webpack/ci.27b78ab0.json
4: "markdownDescription": "Gitlab has a built-in solution for doing CI called Gitlab CI. It is configured by supplying a file called `.gitlab-ci.yml`, which will list all the jobs that are going to run for the project. A full list of all options can be found [here](https://docs.gitlab.com/ee/ci/yaml). [Learn More](https://docs.gitlab.com/ee/ci/index.html).",
./editor/schema/ci-27b78ab0e321dfa26707da6159bf21d0cb18f51fba9b5645ae68449e06ee24e4.json
4: "markdownDescription": "Gitlab has a built-in solution for doing CI called Gitlab CI. It is configured by supplying a file called `.gitlab-ci.yml`, which will list all the jobs that are going to run for the project. A full list of all options can be found [here](https://docs.gitlab.com/ee/ci/yaml). [Learn More](https://docs.gitlab.com/ee/ci/index.html).",
The use-case and applications seem small, for one needs to have a specific URL they would need static as well as a reason for it, however having an option to ensure assets are static in terms of their name is a feature-request nonetheless.