Dear Jorge,
we need some more info, that’s a bit vague. I know it might sound annoying, but the usual things such as:
I know a few of the above things are written in the manual already and would be implicit, but it might happen that a user overlooks them, or misinterprets them. That’s why repeating the steps done helps to understand where the problem is
Kind Regards,
Armando
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
vocbench-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vocbench-user/6a76e746-508e-4cd5-8e28-16e6b94814fdn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/AS2PR03MB9889E1E2A3FD206AF9B27326C7592%40AS2PR03MB9889.eurprd03.prod.outlook.com.
Dear Thomas,
Thanks so much for the additional information.
While I might be wrong in confirming (I’ll wait for some colleague to correct me in case), I believe you are right, the /semanticturkey can’t be changed.
What we usually do depends on the scenario. With containers you have already different environments or, plainly, on the same server, you can use different ports. Then, the common solution is putting a reverse proxy providing, externally, different paths (or different sub-domains as you did).
The client can configure the path, as you can see from the st_path variable here:
https://bitbucket.org/art-uniroma2/vocbench3/src/master/src/vbconfig.js
and the URL shape here:
https://semanticturkey.uniroma2.it/doc/user/web_api.jsf#services_address_structure
which seem to confirm the presence of /semanticturkey but, as you say, could have a different part before it (not just the domain) if properly reverse-proxied.
I’ll ask other colleagues who are dealing more often with system configuration so they can complete with more detailed info.
Kind Regards,
Armando