Fixes #3629: Updating package-based installations can break the front end.
This commit is contained in:
parent
0f3cd3922f
commit
064181815e
2 changed files with 13 additions and 0 deletions
|
@ -116,4 +116,5 @@ env:
|
|||
- ZAMMAD_WEBSOCKET_PORT=6042
|
||||
services:
|
||||
- postgres
|
||||
before_install: contrib/packager.io/preinstall.sh
|
||||
after_install: contrib/packager.io/postinstall.sh
|
||||
|
|
12
contrib/packager.io/preinstall.sh
Executable file
12
contrib/packager.io/preinstall.sh
Executable file
|
@ -0,0 +1,12 @@
|
|||
#!/bin/bash
|
||||
#
|
||||
# packager.io preinstall script
|
||||
#
|
||||
|
||||
#
|
||||
# Make sure that after installation/update there can be only one sprockets manifest,
|
||||
# the one coming from the package. The package manager will ignore any duplicate files
|
||||
# which might come from a backup restore and/or a manual 'assets:precompile' command run.
|
||||
# These duplicates can cause the application to fail, however.
|
||||
#
|
||||
rm -f /opt/zammad/public/assets/.sprockets-manifest-*.json || true
|
Loading…
Reference in a new issue