Hi France,
we decided not to follow the docker path (at the time there wasn't even a way to easily map host os to container users, so you had to work with fixed user ids...).
You can set the path in the Context object, as I've tested here: https://github.com/axxepta/basex-multitenant/blob/master/src/main/java/de/ax...
The idea here is to map the request, eg: /api/customer1/db2 to another Context than /api/customer2
Br, Max
Am Fr., 23. Nov. 2018 um 10:17 Uhr schrieb France Baril france.baril@architextus.com:
Hi,
For one of my projects, we want to set up BaseX as part of an online application. I was wondering if anyone has experience installing BaseX in a Docker setup and if so how things got split up.
In our case, each client will have many database, we're afraid that if we use a single baseX installation, it will have too many attached dbs.
So we were thinking that we could use 1 application but save1 data/repo per client in their own docker unit , then again, since .basex can only link to 1 repo/data, it doesn't seem possible. If you consider 1000 clients with an average of 30 (1 per language) database each, would you use a single installation and manage security at the db level with all dbs for all clients in the same setup or would you suggest 1 full instance (server + set of db) per client?
Links to any case study would be useful too.
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com