DigitaleBibliothek / Frontend / a6be9204e6a

Commits

Alexandre Vryghem authored a6be9204e6a Merge 13 Feb 2023

Merge remote-tracking branch 'upstream/main' into w2p-98855_themeable-file-download-link_contribute-main

# Conflicts:
#	src/themes/custom/eager-theme.module.ts

config/config.example.yml

Modified

-25
+  host: api7.dspace.org
-26
+  port: 443
-27
+  # NOTE: Space is capitalized because 'namespace' is a reserved string in TypeScript
-28
+  nameSpace: /server
-29
-30
+# Caching settings
-31
+cache:
-32
+  # NOTE: how long should objects be cached for by default
-33
+  msToLive:
-34
+    default: 900000 # 15 minutes
--
+  control: max-age=60 # revalidate browser
-+
+  # Default 'Cache-Control' HTTP Header to set for all static content (including compiled *.js files)
-+
+  # Defaults to max-age=604,800 seconds (one week). This lets a user's browser know that it can cache these
-+
+  # files for one week, after which they will be "stale" and need to be redownloaded.
-+
+  # NOTE: When updates are made to compiled *.js files, it will automatically bypass this browser cache, because
-+
+  # all compiled *.js files include a unique hash in their name which updates when content is modified.
-+
+  control: max-age=604800 # revalidate browser
-41
+  autoSync:
-42
+    defaultTime: 0
-43
+    maxBufferSize: 100
-44
+    timePerMethod:
-45
+      PATCH: 3 # time in seconds
-+
+  # In-memory cache(s) of server-side rendered pages. These caches will store the most recently accessed public pages.
-+
+  # Pages are automatically added/dropped from these caches based on how recently they have been used.
-+
+  # Restarting the app clears all page caches.
-+
+  # NOTE: To control the cache size, use the "max" setting. Keep in mind, individual cached pages are usually small (<100KB).
-+
+  # Enabling *both* caches will mean that a page may be cached twice, once in each cache (but may expire at different times via timeToLive).
-+
+  serverSide:
-+
+    # Set to true to see all cache hits/misses/refreshes in your console logs. Useful for debugging SSR caching issues.
-+
+    debug: false
-+
+    # When enabled (i.e. max > 0), known bots will be sent pages from a server side cache specific for bots.
-+
+    # (Keep in mind, bot detection cannot be guarranteed. It is possible some bots will bypass this cache.)
-+
+    botCache:
-+
+      # Maximum number of pages to cache for known bots. Set to zero (0) to disable server side caching for bots.
-+
+      # Default is 1000, which means the 1000 most recently accessed public pages will be cached.
-+
+      # As all pages are cached in server memory, increasing this value will increase memory needs.
-+
+      # Individual cached pages are usually small (<100KB), so max=1000 should only require ~100MB of memory.
-+
+      max: 1000
-+
+      # Amount of time after which cached pages are considered stale (in ms). After becoming stale, the cached
-+
+      # copy is automatically refreshed on the next request.
-+
+      # NOTE: For the bot cache, this setting may impact how quickly search engine bots will index new content on your site.
-+
+      # For example, setting this to one week may mean that search engine bots may not find all new content for one week.
-+
+      timeToLive: 86400000 # 1 day
-+
+      # When set to true, after timeToLive expires, the next request will receive the *cached* page & then re-render the page
-+
+      # behind the scenes to update the cache. This ensures users primarily interact with the cache, but may receive stale pages (older than timeToLive).
-+
+      # When set to false, after timeToLive expires, the next request will wait on SSR to complete & receive a fresh page (which is then saved to cache).
-+
+      # This ensures stale pages (older than timeToLive) are never returned from the cache, but some users will wait on SSR.
-+
+      allowStale: true
-+
+    # When enabled (i.e. max > 0), all anonymous users will be sent pages from a server side cache.
-+
+    # This allows anonymous users to interact more quickly with the site, but also means they may see slightly
-+
+    # outdated content (based on timeToLive)
-+
+    anonymousCache:
-+
+      # Maximum number of pages to cache. Default is zero (0) which means anonymous user cache is disabled.
-+
+      # As all pages are cached in server memory, increasing this value will increase memory needs.
-+
+      # Individual cached pages are usually small (<100KB), so a value of max=1000 would only require ~100MB of memory.
-+
+      max: 0
-+
+      # Amount of time after which cached pages are considered stale (in ms). After becoming stale, the cached
-+
+      # copy is automatically refreshed on the next request.
-+
+      # NOTE: For the anonymous cache, it is recommended to keep this value low to avoid anonymous users seeing outdated content.
-+
+      timeToLive: 10000 # 10 seconds
-+
+      # When set to true, after timeToLive expires, the next request will receive the *cached* page & then re-render the page
-+
+      # behind the scenes to update the cache. This ensures users primarily interact with the cache, but may receive stale pages (older than timeToLive).
-+
+      # When set to false, after timeToLive expires, the next request will wait on SSR to complete & receive a fresh page (which is then saved to cache).
-+
+      # This ensures stale pages (older than timeToLive) are never returned from the cache, but some users will wait on SSR.
-+
+      allowStale: true
-89
-90
+# Authentication settings
-91
+auth:
-92
+  # Authentication UI settings
-93
+  ui:
-94
+    # the amount of time before the idle warning is shown
-95
+    timeUntilIdle: 900000 # 15 minutes
-96
+    # the amount of time the user has to react after the idle warning is shown before they are logged out.
-97
+    idleGracePeriod: 300000 # 5 minutes
-98
+  # Authentication REST settings

Frontend

Commits

Jira Issues

Add shortcut