|
1 | 1 | # NOTE: will log all redux actions and transfers in console |
2 | 2 | debug: false |
3 | 3 |
|
4 | | -# Angular Universal server settings |
| 4 | +# Angular User Inteface settings |
5 | 5 | # NOTE: these settings define where Node.js will start your UI application. Therefore, these |
6 | 6 | # "ui" settings usually specify a localhost port/URL which is later proxied to a public URL (using Apache or similar) |
7 | 7 | ui: |
|
17 | 17 | # Trust X-FORWARDED-* headers from proxies (default = true) |
18 | 18 | useProxies: true |
19 | 19 |
|
| 20 | +# Angular Universal / Server Side Rendering (SSR) settings |
20 | 21 | universal: |
21 | | - # Whether to inline "critical" styles into the server-side rendered HTML. |
22 | | - # Determining which styles are critical is a relatively expensive operation; |
23 | | - # this option can be disabled to boost server performance at the expense of |
24 | | - # loading smoothness. For improved SSR performance, DSpace defaults this to false (disabled). |
| 22 | + # Whether to tell Angular to inline "critical" styles into the server-side rendered HTML. |
| 23 | + # Determining which styles are critical is a relatively expensive operation; this option is |
| 24 | + # disabled (false) by default to boost server performance at the expense of loading smoothness. |
25 | 25 | inlineCriticalCss: false |
| 26 | + # Path prefixes to enable SSR for. By default these are limited to paths of primary DSpace objects. |
| 27 | + # NOTE: The "/handle/" path ensures Handle redirects work via SSR. The "/reload/" path ensures |
| 28 | + # hard refreshes (e.g. after login) trigger SSR while fully reloading the page. |
| 29 | + paths: [ '/home', '/items/', '/entities/', '/collections/', '/communities/', '/bitstream/', '/bitstreams/', '/handle/', '/reload/' ] |
| 30 | + # Whether to enable rendering of Search component on SSR. |
| 31 | + # If set to true the component will be included in the HTML returned from the server side rendering. |
| 32 | + # If set to false the component will not be included in the HTML returned from the server side rendering. |
| 33 | + enableSearchComponent: false |
| 34 | + # Whether to enable rendering of Browse component on SSR. |
| 35 | + # If set to true the component will be included in the HTML returned from the server side rendering. |
| 36 | + # If set to false the component will not be included in the HTML returned from the server side rendering. |
| 37 | + enableBrowseComponent: false |
| 38 | + # Enable state transfer from the server-side application to the client-side application. |
| 39 | + # Defaults to true. |
| 40 | + # Note: When using an external application cache layer, it's recommended not to transfer the state to avoid caching it. |
| 41 | + # Disabling it ensures that dynamic state information is not inadvertently cached, which can improve security and |
| 42 | + # ensure that users always use the most up-to-date state. |
| 43 | + transferState: true |
| 44 | + # When a different REST base URL is used for the server-side application, the generated state contains references to |
| 45 | + # REST resources with the internal URL configured. By default, these internal URLs are replaced with public URLs. |
| 46 | + # Disable this setting to avoid URL replacement during SSR. In this the state is not transferred to avoid security issues. |
| 47 | + replaceRestUrl: true |
26 | 48 |
|
27 | 49 | # The REST API server settings |
28 | 50 | # NOTE: these settings define which (publicly available) REST API to use. They are usually |
|
33 | 55 | port: 443 |
34 | 56 | # NOTE: Space is capitalized because 'namespace' is a reserved string in TypeScript |
35 | 57 | nameSpace: /server |
| 58 | + # Provide a different REST url to be used during SSR execution. It must contain the whole url including protocol, server port and |
| 59 | + # server namespace (uncomment to use it). |
| 60 | + #ssrBaseUrl: http://localhost:8080/server |
36 | 61 |
|
37 | 62 | # Caching settings |
38 | 63 | cache: |
@@ -431,6 +456,29 @@ comcolSelectionSort: |
431 | 456 | sortField: 'dc.title' |
432 | 457 | sortDirection: 'ASC' |
433 | 458 |
|
| 459 | +# Live Region configuration |
| 460 | +# Live Region as defined by w3c, https://www.w3.org/TR/wai-aria-1.1/#terms: |
| 461 | +# Live regions are perceivable regions of a web page that are typically updated as a |
| 462 | +# result of an external event when user focus may be elsewhere. |
| 463 | +# |
| 464 | +# The DSpace live region is a component present at the bottom of all pages that is invisible by default, but is useful |
| 465 | +# for screen readers. Any message pushed to the live region will be announced by the screen reader. These messages |
| 466 | +# usually contain information about changes on the page that might not be in focus. |
| 467 | +liveRegion: |
| 468 | + # The duration after which messages disappear from the live region in milliseconds |
| 469 | + messageTimeOutDurationMs: 30000 |
| 470 | + # The visibility of the live region. Setting this to true is only useful for debugging purposes. |
| 471 | + isVisible: false |
| 472 | + |
| 473 | + |
| 474 | +# Search settings |
| 475 | +search: |
| 476 | + # Number used to render n UI elements called loading skeletons that act as placeholders. |
| 477 | + # These elements indicate that some content will be loaded in their stead. |
| 478 | + # Since we don't know how many filters will be loaded before we receive a response from the server we use this parameter for the skeletons count. |
| 479 | + # e.g. If we set 5 then 5 loading skeletons will be visualized before the actual filters are retrieved. |
| 480 | + defaultFiltersCount: 5 |
| 481 | + |
434 | 482 | crisLayout: |
435 | 483 | urn: |
436 | 484 | - name: doi |
|
0 commit comments