Fixes #6

Root cause: Every readiness check triggered a cache warming
Solution: Move readiness to startup probe

Root cause: Due to the timeout, every request that was launched while fetching the previous manifests could led to another fetch and another cache.warmup
Solution: Be more synchronous

Root cause: Hash was computed on array.toString() which does not change much.
Solution: Use the actual content of the vite manifests to compute the version.

This prevents unnesessary large headers as the UI will filter for CSS files only

richard.petersen authored 3 years ago and julian.baeume committed 3 years ago

Includes the version string and dependencies

Signed-off-by: Julian Bäume <julian.baeume@open-xchange.com>

this can not only be handled on ingress level, but we need to mount the
express app also on the app root level. This basically just works out of the
box.

Promise.race resolve or rejects with the first promise that answers.
We now return the first promise that fulfills after all promises have
settled.

this is an implicit endpoint served by us.

remove /api prefix and be more restful. This should help to simplify ingress objects

first hit wins. This allows us to transparently use sourcemaps and other files that
are not part of the sources according to the vite manifest

this will mark the pod "ready", once the cache is warm.
This will remove the penality for the very first to this service, because
it will not receive any traffic until the cache is warm.

we want to have the changes rolled out, so we disable CSP headers for now and
will take care of them after the file_cache functionality has been rolled out

just for testing purposes, disable CSP for now until sha calculation is fixed

this currently doesn't really work as expected, but can be used as a base
to properly implement CSP for the scripts we "know" about.

the file cache is populated with data defined in the manifest files configured for
all components and will basically fetch everything from all components. This allows
us to use this manifest service as the only source of truth for UI related sources and
simplifies ingres setup a lot.

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

this got lost when implementation changed to base data on vite manifests but should
still be part of the manifest.json file

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

those files are supposed to be downloaded directly

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

… and transform them to something that can be consumed by App Suite.

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

since it's still kind of small, it makes sense to switch to ESM, now.