Request for BFS tenanted deploy of DE
BFS's required configurations/customisations:
DE
- assets.header (logo): /uploads/8aec091dff89b28949e9681a81b131e9/logo_explorer.png
- app.title: FR: "OFS Data Explorer", DE: "BFS Data Explorer", IT: "UFS Data Explorer", EN: "FSO Data Explorer"
- CategoryScheme(s) to be used for search indexing: http://nsi-stable-siscc.redpelicans.com/rest/categoryscheme/CH1/TOPICS/1.0
- home page facets (CategoryScheme(s), Codelist(s)): "Thème", "Thema", "Tema", "Topic"
DLM
- default.
Other
- Languages: French,Italian,English
-
New German locale
Application/services list:
- reusing common SIS-CC staging NSI ws 'SIS-CC-stable' with stable content (upgraded database) http://nsi-stable-siscc.redpelicans.com/
- reusing common SIS-CC staging DLM http://dlm-staging-siscc.redpelicans.com/
- reusing common staging Transfer ws http://transfer-siscc.redpelicans.com/swagger/index.html
- reusing common staging Authorisation ws http://authz-siscc.redpelicans.com/swagger/index.html
-
‘BFS’ tenant of DE (http://de-staging-bfs.redpelicans.com/) plugged to 'SIS-CC-stable' and with BFS-specific search based on categoryscheme -
also create alias http://de-demo-bfs.siscc.org/ for http://de-staging-bfs.redpelicans.com/
how to add a tenant:
- add new tenant in config repo (code)
- update route(s) in proxy repo (code)
- update cname(s) for wanted domain(s) in respective registrar(s) (online)
- update keycloak app entries (online)
- restart sfs if datasources updated
- reindex datasources through sfs API
Edited by Nicolas Briemant