We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post rails upgrade from rails 4 too rails 5 font awesome loading path is not correct for more understanding
rails 4
rails 5
My Application.css path(correct path)
Application.css
https://s3_domain/s3_bucket_name/project_name/assets/admin-fingerprint.css Request Method: GET
Rendered 403 font awesome
403
https://s3_domain/assets/fontawesome-webfont-fingerprint.woff2 Request Method: GET
Ideally correct path should be->
https://s3_domain/s3_bucket_name/project_name/assets/fontawesome-webfont-fingerprint.woff2 Request Method: GET
* autoprefixer-rails (10.4.7.0) * aws-sdk-emrserverless (1.2.0) * aws-sdk-iotwireless (1.27.0) * aws-sdk-redshiftserverless (1.4.0) * aws-sdk-serverlessapplicationrepository (1.44.0) * bootstrap-sass (3.3.5) * coffee-rails (4.2.1) * factory_girl_rails (4.9.0) * font-awesome-rails (4.7.0.8) * jquery-fileupload-rails (1.0.0) * jquery-minicolors-rails (2.2.6.2) * jquery-rails (4.5.0) * minitest-rails (3.0.0) * pry-rails (0.3.9) * rails (5.1.0) * rails-controller-testing (1.0.5) * rails-dom-testing (2.0.3) * rails-html-sanitizer (1.4.3) * rails_request_id (0.1.2 1d52818) * redis-rails (5.0.2) * rspec-rails (4.0.0) * sass (3.7.4) * sass-listen (4.0.0) * sass-rails (6.0.0) * sassc (2.4.0) * sassc-rails (2.1.2) * slim-rails (3.5.1) * sprockets-rails (3.2.2)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Post rails upgrade from
rails 4
toorails 5
font awesome loading path is not correct for more understandingMy
Application.css
path(correct path)Rendered
403
font awesomeIdeally correct path should be->
The text was updated successfully, but these errors were encountered: