Skip to content

Commit

Permalink
Release 1.8.0
Browse files Browse the repository at this point in the history
  • Loading branch information
MarekSuchanek committed Mar 10, 2021
1 parent 0f611c3 commit 141e03f
Show file tree
Hide file tree
Showing 6 changed files with 21 additions and 15 deletions.
2 changes: 1 addition & 1 deletion docs/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
author = 'Dutch Techcentre for Life Sciences'

# The full version, including alpha/beta/rc tags
release = '1.7.0'
release = '1.8.0'


# -- General configuration ---------------------------------------------------
Expand Down
4 changes: 2 additions & 2 deletions docs/deployment/advanced-configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -230,13 +230,13 @@ have to set ``PUBLIC\_PATH`` ENV variable, in this example to
version: '3'
services:
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
volumes:
- ./application.yml:/fdp/application.yml:ro
# ... other volumes
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
ports:
- 80:80
environment:
Expand Down
16 changes: 8 additions & 8 deletions docs/deployment/local-deployment.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,10 @@ Here is an example of the simplest `Docker Compose <https://docs.docker.com/comp
services:
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
ports:
- 80:80
environment:
Expand Down Expand Up @@ -67,12 +67,12 @@ Then, we need to mount the application config into the FDP container and update
services:
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
volumes:
- ./application.yml:/fdp/application.yml:ro
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
ports:
- 8080:80
environment:
Expand Down Expand Up @@ -105,10 +105,10 @@ Here is the updated docker-compose file:
services:
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
ports:
- 80:80
environment:
Expand Down Expand Up @@ -153,12 +153,12 @@ We now need to update our ``docker-compose.yml`` file, we add a new volume for t
services:
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
volumes:
- ./application.yml:/fdp/application.yml:ro
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
ports:
- 80:80
environment:
Expand Down
4 changes: 2 additions & 2 deletions docs/deployment/production-deployment.rst
Original file line number Diff line number Diff line change
Expand Up @@ -101,12 +101,12 @@ We have certificates generated and configuration for proxy ready. Now we need to
- /etc/letsencrypt:/etc/letsencrypt:ro
fdp:
image: fairdata/fairdatapoint:1.7.0
image: fairdata/fairdatapoint:1.8.0
volumes:
- ./application.yml:/fdp/application.yml:ro
fdp-client:
image: fairdata/fairdatapoint-client:1.7.0
image: fairdata/fairdatapoint-client:1.8.0
environment:
- FDP_HOST=fdp
Expand Down
6 changes: 6 additions & 0 deletions docs/development/changelog.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ Overview

Here we summarize the key features and changes for each FAIR Data Point release. For details including bugfixes and minor changes, see :ref:`detailed-changelog`.

1.8.0
-----

- Added Admin UI to FDP Index with possibility to trigger metadata retrieval, change settings, or delete entry
- Several bug fixes and dependencies updated (including Java 15)

1.7.0
-----

Expand Down
4 changes: 2 additions & 2 deletions docs/usage/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -107,12 +107,12 @@ The `DASH <http://datashapes.org/dash>`_ vocabulary introduces extensions to the
dash:editor dash:TextFieldEditor ;
]
By adding a ``dash:viewer`` statement, the user interface is instructed to show the property value when the resource metadata is displayed. Removing a ``dash:viewer`` statement will instruct the user interface will not render the property value at all. The value will still be present in the metadata model. The supported set of viewers (version 1.6.0):
By adding a ``dash:viewer`` statement, the user interface is instructed to show the property value when the resource metadata is displayed. Removing a ``dash:viewer`` statement will instruct the user interface will not render the property value at all. The value will still be present in the metadata model. The supported set of viewers:

* ``sh:LabelViewer``
* ``sh:URIViewer``

By adding a ``dash:editor`` statement, the editor form in the user interface will show an edit field for the property. Removing a ``dash:editor`` statement will prevent the property from being edited. This could be intended behaviour for properties that are generated server side. The supported set of editors (version 1.6.0):
By adding a ``dash:editor`` statement, the editor form in the user interface will show an edit field for the property. Removing a ``dash:editor`` statement will prevent the property from being edited. This could be intended behaviour for properties that are generated server side. The supported set of editors:

* ``sh:TextFieldEditor``
* ``sh:TextAreaEditor``
Expand Down

0 comments on commit 141e03f

Please sign in to comment.