Assets not being created

I’ve upgraded Zammad into the latest version (congrats on using npm + yarn that aren’t normally available on Debian Stretch) and now I can’t log in into the admin panel because assets aren’t present. I’ve tried with: “export RAILS_SERVE_STATIC_FILES=false” and with “export RAILS_SERVE_STATIC_FILES=true”, but it doesn’t make any difference. There are no static files in the /assets/ directory and I can’t do anything to load into the service:

<link rel="stylesheet" media="all" href="/assets/application-65986ce4bad6ba785d86acfd7f5085b64b2c7acdd80c3b4b7a9113a9b9f8d3c7.css" /> <link rel="stylesheet" media="print" href="/assets/application-print-25adf1ad928517e8672a95590d5449b40243c7ae6749c73d532f8fcc068c2612.css" /> <script src="[/assets/application-1cbd2cb156b3dcd729f33be44bce6d193d38778f46dd24ac19333a1d907d9917.js" defer="defer"></script>

All of these gives 404 error.

Edit: Of course I’m using rake assets:precompile:

yarn install v1.17.3
[1/4] Resolving packages…
success Already up-to-date.
Done in 0.20s.

Please provide the console output of rake assets:precompile.
Also, please fill in the template information below (edit your first article for that), because these information are mandatory for anything further:

* Used Zammad version: 
* Used Zammad installation source: (source, package, ...)
* Operating system: 
* Browser + version: 

The assets you’re searching for will life in:

Also, while you’re at providing information, please also provide your nginx/apache configuration for Zammad (the vhost).

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.