[DRE-maint] Bug#1101504: redmine: served via unicorn and nginx, errors due to 'GET /assets/...'

[Jörg-Volker Peetz]

Hi Soren,

thanks for looking into this.

Soren Stoutner wrote on 28/03/2025 18:07:
> Volker,
>
> On Friday, March 28, 2025 7:42:40 AM Mountain Standard Time Jörg-
> Volker Peetz wrote:
>> Package: redmine
>> Version: 6.0.4+ds-1
>> Severity: normal
>>
>> Dear Debian Ruby Team, dear Soren Stoutner,
>>
>> many thanks for all the work to upgrade redmine to version 6.
>> My configuration which serves redmine via unicorn and nginx in a
>> sub-uri /redmine, seems to work.
>>
>> But it still sees errors in the log file due to a 'GET /access/...'.
>> The normal access is 'GET /redmine/...', e.g., 'GET
>> /redmine/assests/gantt-757adf6f.js' which is handled via an alias
>> in the nginx configuration (just as documented in
>> '/usr/share/doc/examples/nginx-alaias.conf').
>>
>> For the sub-uri config I have slightly changed
>> /usr/share/redmine/config.ru using
>>
>> map ENV['RAILS_RELATIVE_URL_ROOT'] || '/' do
>>     run Rails.application
>> end
>>
>> instead of just
>>
>> run Rails.application
>
> Thank you for the detailed bug report.
>
> Does this feel like an upstream bug to you?

Yes. And meanwhile, I found this in the redmine issues:

Defect #41734 wrong url for assets in public/assets
https://www.redmine.org/issues/41734

It is known upstream. And as far as I understand, after choosing a sub-uri I
have to re-generate the files in the /var/cache/redmine/default/public/assets
directory. The wrong path is embedded in the css files in that directory.

How could this re-generation be accomplished? Maybe, every time before deploying
redmine?

Regards,
Jörg.