Skip to content

getting_started.md

Latest commit

 

History

History
107 lines (81 loc) · 3.18 KB

getting_started.md

File metadata and controls

107 lines (81 loc) · 3.18 KB
Raw

Getting started

chbrandt/dachs

The latest (Docker) image provides the (DaCHS) service as a whole, encapsulating dachs-server and postgresql dbms in the same container.

By default, DaCHS provides an HTML/GUI interface at port 8080, on running the container you want to map the container's port (8080) to some on the host:

(host)$ docker run -it --name dachs -p 8080:8080 chbrandt/dachs

, where we made an identity map (host's 8080 to container's 8080).

Inside the container, to start the services work like in a normal machine:

(dock)$ service postgresql start
(dock)$ service dachs start

. You can also use a convenience dachs.sh script to start everything for you:

(dock)$ /dachs.sh start

Go to your host's 'http://localhost:8080' to check DaCHS front-page.

To make a directory from the host system available from the container one can use the option argument '-v' to mount a volume at given location inside the container:

(host)$ docker run -it --name dachs -p 80:8080 \
                   -v /data/inputs/resourceX:/var/gavo/inputs/resourceX \
                   chbrandt/dachs

You can mount as many volumes (directories) as you want.

Inside the container, you can use dachs as you would on an usual machine. For instance, run DaCHS and load/pub "resourceX":

(dock)$ service postgresql start
(dock)$ service dachs start
(dock)$
(dock)$ cd /var/gavo/inputs
(dock)$ gavo imp resourceX/q.rd
(dock)$ gavo pub resourceX/q.rd
(dock)$
(dock)$ service dachs reload

Test migration

If you're using the container to test a new version to eventually migrate your datasets to, you'll likely want to mount your VO/DaCHS resources as in the example above. To add security to your data -- if they are being shared with the data resource live in production -- you may want to use 'ro' (read-only) as an option for mounting points:

(host)$ docker run -v /data/rd/input:/var/gavo/inputs/input:ro \
                   -it --name dachs -p 80:8080 \
                   chbrandt/dachs

And then do the imports, publications, data access tests necessary to check for compatibility; and eventually migrate to the new version if/when everything is fine.

DaCHS 2

  • Docker image tags: latest, 2.1 (previously, beta)

DaCHS' version 2 is available as a beta version, which runs on Python-3. Because it is a major upgrade dachs has gone through, it is a good idea to test your data and services as extensively as possible.

To use the new version, just have to use the beta image:

(host)$ docker run -v /data/rd/input:/var/gavo/inputs/input:ro \
                   -it --name dachs -p 80:8080 \
                   chbrandt/dachs:beta

Everything should feel the same. Start docker (here through the convenience script left in your container's '/'), and use/test it as usual:

(dock)$ /dachs.sh start
9.6/main (port 5432): down
[ ok ] Starting PostgreSQL 9.6 database server: main.
[ ok ] Starting VO server: dachs.
(dock)$
(dock)$ dachs --version
Software (2.0.4) Schema (23/23)

/.\