Hey everybody,
I have a basex/basexhttp:8.5.1 production container running. To access the dba web interface I created a basex/dba container and connected it to the same docker network. On the http://host:18984/dba/login http://host:18984/dba/login was an input box to connect to a remote BaseX server instance but with the latest basex/dba: image (8.6.1 beta) this is gone
How am I now supposed to access the dba web ui ?
Thanks in advance
Björn
Hi Björn,
The old RESTXQ code led to increased numbers of system-wide read/write locks. This is why support for remote connections was removed. It’s good to know that people like you were using it, and we are definitely interested in reintroducing it in revised form in future. Until then, feel free to work with the DBA code of previous versions of BaseX, it is still functional.
Cheers, Christian
On Wed, Feb 1, 2017 at 10:17 AM, Braunschweig, Björn bjoern.braunschweig@gwdg.de wrote:
Hey everybody,
I have a basex/basexhttp:8.5.1 production container running. To access the dba web interface I created a basex/dba container and connected it to the same docker network. On the http://host:18984/dba/login was an input box to connect to a remote BaseX server instance but with the latest basex/dba: image (8.6.1 beta) this is gone…
How am I now supposed to access the dba web ui ?
Thanks in advance Björn
Hi Christian,
Thanks for your quick response :-)
I don’t quite understand your answer. a) Does this mean that since Version 8.6 there is no officially supported web interface for basex? b) What is the difference between the basex/basexhttp and basex/dba images? (I think the documentation at https://hub.docker.com/r/basex/basexhttp/ is now misleading)
Regards Björn
-----Ursprüngliche Nachricht----- Von: Christian Grün [mailto:christian.gruen@gmail.com] Gesendet: Mittwoch, 1. Februar 2017 10:37 An: Braunschweig, Björn bjoern.braunschweig@gwdg.de Cc: basex-talk@mailman.uni-konstanz.de Betreff: Re: [basex-talk] Cannot access basex instance with latest basex/dba image
Hi Björn,
The old RESTXQ code led to increased numbers of system-wide read/write locks. This is why support for remote connections was removed. It’s good to know that people like you were using it, and we are definitely interested in reintroducing it in revised form in future. Until then, feel free to work with the DBA code of previous versions of BaseX, it is still functional.
Cheers, Christian
On Wed, Feb 1, 2017 at 10:17 AM, Braunschweig, Björn bjoern.braunschweig@gwdg.de wrote:
Hey everybody,
I have a basex/basexhttp:8.5.1 production container running. To access the dba web interface I created a basex/dba container and connected it to the same docker network. On the http://host:18984/dba/login was an input box to connect to a remote BaseX server instance but with the latest basex/dba: image (8.6.1 beta) this is gone…
How am I now supposed to access the dba web ui ?
Thanks in advance Björn
Hi Björn,
a) Does this mean that since Version 8.6 there is no officially supported web interface for basex?
There still is. DBA is still part of BaseX, but it doesn’t provide means to connect remotely.
b) What is the difference between the basex/basexhttp and basex/dba images? (I think the documentation at https://hub.docker.com/r/basex/basexhttp/ is now misleading)
Personally, I can’t say anything about Docker. Maybe someone else on the list knows more?
Christian
Hi, this is how it used to be:
basex/basexhttp : the standard basex distribution for docker basex/dba: only the DBA project
The idea was to have both running independently where you would connect from /dba to /basexhttp
But this does not work anymore since 8.6
So for the time being, just use basex/dba prior to 8.6
2017-02-01 12:21 GMT+01:00 Christian Grün christian.gruen@gmail.com:
Hi Björn,
a) Does this mean that since Version 8.6 there is no officially supported web interface for basex?
There still is. DBA is still part of BaseX, but it doesn’t provide means to connect remotely.
b) What is the difference between the basex/basexhttp and basex/dba images? (I think the documentation at https://hub.docker.com/r/basex/basexhttp/ is now misleading)
Personally, I can’t say anything about Docker. Maybe someone else on the list knows more?
Christian
Hi Björn, hi Max,
yes, we kind of missed that not-so-subtle-change: Docker basex/dba is now fixed to the DBA that allows remote connections. https://hub.docker.com/r/basex/dba/ https://hub.docker.com/r/basex/dba/
`docker pull basex/dba:latest`
Should bring back that version.
We are currently figuring out ways to bundle the current dba alongsside `basex/basexhttp`.
I’ll keep you posted.
Best from Konstanz, Michael
Am 01.02.2017 um 14:52 schrieb Maximilian Gärber mgaerber@arcor.de:
Hi, this is how it used to be:
basex/basexhttp : the standard basex distribution for docker basex/dba: only the DBA project
The idea was to have both running independently where you would connect from /dba to /basexhttp
But this does not work anymore since 8.6
So for the time being, just use basex/dba prior to 8.6
2017-02-01 12:21 GMT+01:00 Christian Grün christian.gruen@gmail.com:
Hi Björn,
a) Does this mean that since Version 8.6 there is no officially supported web interface for basex?
There still is. DBA is still part of BaseX, but it doesn’t provide means to connect remotely.
b) What is the difference between the basex/basexhttp and basex/dba images? (I think the documentation at https://hub.docker.com/r/basex/basexhttp/ is now misleading)
Personally, I can’t say anything about Docker. Maybe someone else on the list knows more?
Christian
-- Michael Seiferle, BaseX GmbH, http://www.basexgmbh.de |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Fon: +49 7531 916 82 77
basex-talk@mailman.uni-konstanz.de
-
Braunschweig, Björn -
Christian Grün -
Maximilian Gärber -
Michael Seiferle