You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #1907 - jtgeibel:fastboot-staging-experimental, r=carols10cents
Add a `USE_FASTBOOT=staging-experimental` mode
This adds a new mode to the `USE_FASTBOOT` environment variable. The logic is now:
* When deployed on Heroku (staging or production - via `script/start-web.sh`):
* If `USE_FASTBOOT=staging-experimental` then non-backend requests are sent to FastBoot.
* If `USE_FASTBOOT` is set and non-zero length, FastBoot is enabled only for allowed paths.
* Otherwise (`USE_FASTBOOT` is not set, or is zero length), FastBoot is disabled.
* When doing local development (via `script/ember.sh`):
* If `USE_FASTBOOT` is set, all (initial) frontend requests are served via FastBoot. This is equivalent to `staging-experimental` above.
* If `USE_FASTBOOT` is not set, FastBoot is disabled.
Because our development environment doesn't go through nginx, it isn't possible to support the "FastBoot is enabled only for allowed paths" mode. However, once the frontend has booted, all further requests hit the backend (unless JS is disabled, then every client navigation results in a new request served via FastBoot).
0 commit comments