Closed jessopb closed 5 years ago
staging has this error on npm ci: https://github.com/zkat/cipm/issues/58 while dev2 does not - both hvae the same version of npm and libcipm
Things are building/running fine. DMCA pages respond differently on staging environment (correctly blocks content but the page is not rendered with the full-page 451 as expected.
I still haven't found what's going on, I've rebuilt everything I can find. git clean -fxd
, rebuilt configs, npm cache verify
, npm i -g npm@latest
, etc. Still investigating. At least all environments "work" and prod runs as expected.
I'm going to de-prioritize this. It's not impacting releases at the moment and I have spent more time on this than anticipated.
This is not a build issue, it's bad logic in the app, closing and will open a more specific issue.
There is some difference between staging and dev2 (and a local arch linux environment pulled fresh from master) that causes at a large number of promises to break. Consequently, the AssetBlocked page never shows on content that is supposed to be blocked. factor | staging | dev2 node version | 8.12 | 8.11 ubuntu version| xenial | xenial mysql | running | running
Staging is missing these three config keys:
Staging also has ': false' for its master password.