Hi Soren,
in my last mail I missed two things, so I have two corrections to make:
Soren Stoutner wrote on 31/03/2025 21:50:
Jörg-Volker
On Saturday, March 29, 2025 3:59:22 AM Mountain Standard Time Jörg-
Volker Peetz wrote:
I have added this information to README.Debian.
https://salsa.debian.org/ruby-team/redmine/-/blob/master/debian/
README.Debian?ref_type=heads#L43-55
Yes, I used your hint and refined it a little bit:
First, the old assets have to be removed:
# rm -rf /var/cache/redmine/default/public/assets/*
In the assets directory is at least one dot file (.manifest.json).
Maybe, better do
(cd /var/cache/redmine/default/public ; rm -rf assets ; \
mkdir -m 755 assets ; chown www-data: assets)
then rebuild the assets, taking some wisdom from the
redmine.postinst script:
# su -s <REDMINE_CURRENT_USER> /bin/sh -c "cd /usr/share/redmine
; REDMINE_INSTANCE=<INSTANCE> bundle exec rake assets:precompile
RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT=/<SUB-URI>"
I placed the switch '-s' wrong and maybe, for clarity the arguments should be
reordered. The following works:
su <REDMINHE_CURRENT_USER> -s /bin/sh -c \
"cd /usr/share/redmine ; REDMINE_INSTANCE=<INSTANCE> \
RAILS_ENV=production RAILS_RELATIVE_URL_ROOT=/<SUB-URI> \
bundle exec rake assets:precompile"
And it could be added:
"""
Alternatively, run the following command to configure the assets with alias:
service <REDMINE> restart
which makes use of the fact that by default, Redmine automatically recompiles
assets in production mode when the application is (re-) started.
"""
<snip>
Regards,
Jörg.
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
