Static assets are hardcoded to be readed from /self-hosted/ folder on the init migration

[rafaelromcar-parabol]

Issue - Bug

• How serious is the bug? P2 but must be addressed asap.
• OS: macOS / Linux / Windows / ?
• Browser: Chrome / Safari / Lynx / ? + version
• Node version: node --version
• NPM version: npm --version

When the init migration is run, the static assets are hardcoded to be pulled from the instance domain /self-hosted path, which makes the external file store provider useless. Those static assets, the most basic ones for our application, aren't pushed to the external file store provider. And the clients are pulling them from the web server directly, instead of using a bucket or a CDN. That could provoke slowness or even be an attack vector, risking the application availability.

This only affects newly created instances, created from scratch using Parabol >v8. The init migration should be rebased, in order to fix it, replacing the hardcoded path with a variable, depending on the file store provider.

Problem is here. More information on the Slack thread

Acceptance Criteria (optional)

Static assets are read from their actual location
Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.

[jordanh]

Hi @rafaelromcar-parabol ! I am here to triage this.

Could you give me a bit more context on this finding? What is this bug in the way of?

[rafaelromcar-parabol]

Sorry for that, context added to the issue @jordanh