Worden highlight-js assets niet geüpload naar de S3 bucket?

AI-generated summary

kpums reports that the /highlight-js/... assets are missing from the MinIO S3 bucket in both test and production environments, despite other assets being uploaded successfully via bundle exec rake s3:upload_assets. The issue appears to be that highlight.js is not being included in the asset upload process during container rebuilds. Although the highlighter functions correctly within the container, a workaround has been implemented by modifying /lib/highlight_js.rb to use a direct URL. kpums questions whether this is a bug or if the highlight.js asset is simply not yet integrated into the asset upload workflow.

Hallo,

Ik heb test/prod-instanties met Minio S3-buckets voor opslag van assets/uploadbestanden. Het lijkt erop dat vrijwel alles prima werkt. Maar om de een of andere reden ontbreekt in beide omgevingen /highlight-js/... uit de Minio S3-bucket. Interessant is dat dit het enige asset is (voor zover ik kan nagaan) dat ontbreekt. Vereist het een ander commando dan: bundle exec rake s3:upload_assets om tijdens de build naar de S3-bucket te worden geüpload?

It seems that highlighter still lives okay in container. If I modify /lib/highlight_js.rb as mentioned in this article then it works.

Right now added step to container yml file in run: part, with the fix as workaround till this highlighter asset is also part of components that are uploaded to S3 bucket during build

  - replace:
      filename: /var/www/discourse/lib/highlight_js.rb
      from: '"/highlight-js/#{Discourse.current_hostname}/#{version SiteSetting.highlighted_languages}.js"'
      to: '"https://#{Discourse.current_hostname}/highlight-js/#{Discourse.current_hostname}/#{version SiteSetting.highlighted_languages}.js"'

So, this is a bug or missed/not-yer-redone asset that ./launcher rebuild <container_name> does not include this into asset list that are moved to S3 bucket?