Certainly, I was able to get the container running.

The web.xml threw me off, and then the docs said to use a deprecated command.

On 9/4/20, Markus Wittenberg <wittenb...@axxepta.de> wrote:
> Hi there,
>
> in fact the web.xml is not missing. You should be able to connect to
> basex using the exposed ports. This shouldn't be a problem on localhost.
> Depending on your system configuration on a server you might have to
> provide access to the ports to the web explicitly.
>
> The REST endpoints /rest/* over port 8984 are also activated by default.
>
> If you follow the example Running your own Application/DBA in the
> documentaton you can also use RESTXQ applications.
>
> Best regards,
>
>    Markus
>
> Am 04.09.2020 um 12:11 schrieb Christian Grün:
>> …anyone else around here who uses Docker?
>>
>> On Fri, Sep 4, 2020 at 11:32 AM Nicholas Saunders
>> <saunders.nicho...@gmail.com> wrote:
>>> thanks.  I was able to create the container okay, but how do I connect
>>> to the database?
>>>
>>> What I've done so far is gain root on the container itself and
>>> manually copy files in to add to the db.  Can I perhaps connect to the
>>> db on the container through basex on the host?  Or would that be an
>>> odd approach?
>>>
>>> On 9/3/20, Christian Grün <christian.gr...@gmail.com> wrote:
>>>> Thanks for the observation. I’ll try to get into contact with the guys
>>>> who
>>>> wrote the article and see if this can be updated.
>>>>
>>>>
>>>>
>>>> Nicholas Saunders <saunders.nicho...@gmail.com> schrieb am Fr., 4. Sep.
>>>> 2020, 01:19:
>>>>
>>>>> from what I gather, the link command is deprecated:
>>>>>
>>>>>   it sounds like you are using the link feature. This has been
>>>>> deprecated for years. instead, use a   v2 or v3 docker-compose.yml
>>>>> file (if using compose) or if using a different system, simply put
>>>>> both containers on the same        │
>>>>>
>>>>> so the documentation is out of date.
>>>>>
>>>>> On 9/3/20, Christian Grün <christian.gr...@gmail.com> wrote:
>>>>>> Hi Nicholas,
>>>>>>
>>>>>> Have you already worked through the Docker documentation in our Wiki
>>>>>> [1]?
>>>>>>
>>>>>> Best,
>>>>>> Christian
>>>>>>
>>>>>> [1] https://docs.basex.org/wiki/Docker
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 3, 2020 at 4:23 PM Nicholas Saunders
>>>>>> <saunders.nicho...@gmail.com> wrote:
>>>>>>> I've just opened an issue:
>>>>>>>
>>>>>>> https://github.com/BaseXdb/basex/issues/1936
>>>>>>>
>>>>>>> based on an inability to run the docker image:
>>>>>>>
>>>>>>> https://devops.stackexchange.com/q/12338/23443
>>>>>>>
>>>>>>>
>>>>>>> but thought I'd ask here if there might be something obvious.  I'm
>>>>>>> creating the container from the hub image with:
>>>>>>>
>>>>>>> docker run -d \
>>>>>>>      --name basexhttp \
>>>>>>>      --publish 1984:1984 \
>>>>>>>      --publish 8984:8984 \
>>>>>>>      --volume "$HOME/basex/data":/srv/basex/data \
>>>>>>>      --volume "$HOME/basex/repo":/srv/basex/repo \
>>>>>>>      --volume "$HOME/basex/webapp":/srv/basex/webapp \
>>>>>>>      basex/basexhttp:latest
>>>>>>>
>>>>>>>
>>>>>>> and another person reported the missing file.  Is the file missing?
>>>>>>> I'm not sure.
>
> --
> Markus Wittenberg
>
> Tel +49 (0)341 248 475 36
> Mail wittenb...@axxepta.de
>
> ----
>
> axxepta solutions GmbH
> Lehmgrubenweg 17, 88131 Lindau
>
> Amtsgericht Berlin HRB 97544B
> Geschäftsführer: Karsten Becke, Maximilian Gärber
>
>

Reply via email to