Closed oellers closed 5 months ago
The main purpose of the current behavior seems to come from the need to identify a language, so Skohub Vocabs knows which language to select and render.
We can maybe bypass this using the browsers navigator.language
(https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language).
This would also allow us to be independent of a specific web server (Apache), which I would really like.
I have manually modified the .htaccess
file resulting from the build to
Options +FollowSymLinks +MultiViews +Indexes
DirectoryIndex index scheme
AddLanguage da .da
AddLanguage de .de
AddLanguage en .en
AddLanguage fr .fr
AddLanguage nl .nl
AddLanguage sv .sv
AddType text/index .index
AddType application/json .json
AddType application/ld+json .jsonld
(the AddType
directives have been there before)
The second and third point are likely to vary from vocabulary to vocabulary, but during building we should have knowledge of these things. Maybe create an .htaccess
file automatically. If the user runs nginx, caddy or something else, they at least have an indication of what they'd need to implement in their webserver's configuration.
Situation
skohub/skohub-vocabs-docker:latest
provides language-based html files, no general "index.html" (as found in skohub-docker-vocabs#7)Drawbacks
Non-working Example
Working Example
How to deal with the drawback