Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update biothing-studio image tag to 0.4a with Biothing SDK release 0.11.x #50

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −6
Open

Update biothing-studio image tag to 0.4a with Biothing SDK release 0.11.x #50

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/tutorial/studio_guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Docker Hub registry, and can be pulled using:

.. code:: bash

$ docker pull biothings/biothings-studio:0.2a
$ docker pull biothings/biothings-studio:0.4a

.. image:: ../_static/hubstack.png
:width: 100%
Expand Down Expand Up @@ -278,7 +278,7 @@ Note each time a parameter is changed, **Hub** needs to be restarted, as shown o
4. Data plugin architecture and specifications
===========================================

**BioThings Studio** allows to easily define and register datasources using *data plugins*. As of **BioThings Studio 0.2b**, there are two
**BioThings Studio** allows to easily define and register datasources using *data plugins*. As of **BioThings Studio 0.4a**, there are two
different types of data plugin.

4.1. Manifest plugins
Expand Down
8 changes: 4 additions & 4 deletions docs/tutorial/studio_tutorial.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ to a fully operational BioThings API. In a second part, this API will enrich for

.. note:: You may also want to read the `developer's guide <studio_guide.html>`_ for more detailed informations.

.. note:: The following tutorial is only valid for **BioThings Studio** release **0.2b**. Check
.. note:: The following tutorial is only valid for **BioThings Studio** release `0.4a <https://github.com/biothings/biothings_studio/releases/tag/0.4a>`_ which based on Biothing SDK `release 0.11.x <https://github.com/biothings/biothings.api/commits/0.11.x>`_. Check
all available `releases <https://github.com/biothings/biothings_studio/releases>`_ for more.

=================
Expand Down Expand Up @@ -56,7 +56,7 @@ using ``-g`` option:

.. code:: bash

$ docker pull biothings/biothings-studio:0.2b
$ docker pull biothings/biothings-studio:0.4a

A **BioThings Studio** instance exposes several services on different ports:

Expand All @@ -76,9 +76,9 @@ having to enter the container:
.. code:: bash

$ docker run --rm --name studio -p 8080:8080 -p 7022:7022 -p 7080:7080 -p 7081:7081 -p 9200:9200 \
-p 27017:27017 -p 8000:8000 -p 9000:9000 -p 60080:60080 -d biothings/biothings-studio:0.2b
-p 27017:27017 -p 8000:8000 -p 9000:9000 -p 60080:60080 -d biothings/biothings-studio:0.4a

.. note:: we need to add the release number after the image name: biothings-studio:**0.2b**. Should you use another release (including unstable releases,
.. note:: we need to add the release number after the image name: biothings-studio:**0.4a**. Should you use another release (including unstable releases,
tagged as ``master``) you would need to adjust this parameter accordingly.

.. note:: Biothings Studio and the Hub are not designed to be publicly accessible. Those ports should **not** be exposed. When
Expand Down