-
Notifications
You must be signed in to change notification settings - Fork 31
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.
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 README #515
Closed
Closed
update README #515
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
eb007dc
update README
will-moore 9c5110e
Dockerfile to use omero-web-standalone:5.21.0 for Django 3.6
will-moore 43e4aee
Use OMEROHOST env name
will-moore e264b8b
Further tweaks to Docker instructions in README. Use omero-web-standa…
will-moore 257f00d
Use FROM openmicroscopy/omero-web-standalone:5.21.0 Dockerfile
will-moore f35ae2e
remove 'without installing anything'
will-moore 6b9416e
Clarify usage of grunt with Docker
will-moore ec524fb
More README Docker info tweaks
will-moore 2659ac0
Add note to run docker in a different terminal after grunt watch
will-moore a6940e1
Run grunt in different terminal that doesn't have OMEROHOST
will-moore File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -163,35 +163,61 @@ with: | |||||
|
||||||
$ grunt watch | ||||||
|
||||||
It is also possible to develop figure in docker without installing anything locally. | ||||||
The Docker image is built on top of ``openmicroscopy/omero-web-standalone:latest``, so you will have a fully functional | ||||||
omero-web environment while developing ``omero-figure``. | ||||||
First build the Docker image: | ||||||
|
||||||
Local install | ||||||
************* | ||||||
|
||||||
You need an `omero-web` environment. You can either install it locally or use Docker (see below). | ||||||
To install locally, we recommend that you use `conda` to install `omero-py` as described | ||||||
at https://github.com/ome/omero-py and then perform a developer install of `omero-figure` | ||||||
which will include `omero-web`: | ||||||
|
||||||
:: | ||||||
|
||||||
$ docker build -t figure-devel . | ||||||
$ cd omero-figure | ||||||
$ pip install -e . | ||||||
|
||||||
See instructions at https://omero.readthedocs.io/en/latest/developers/Web/Deployment.html | ||||||
for running the development server. | ||||||
|
||||||
Using Docker | ||||||
************ | ||||||
|
||||||
It is also possible to develop figure in docker without creating a python environment locally. | ||||||
The Docker image at ``omero-figure/Dockerfile`` is built on top of | ||||||
`openmicroscopy/omero-web-standalone:latest <https://hub.docker.com/r/openmicroscopy/omero-web-standalone>`_, | ||||||
so you will have a fully functional omero-web environment while developing ``omero-figure``. | ||||||
First build the Docker image and specify the server you wish to connect to: | ||||||
|
||||||
To develop ``omero-figure`` you can either make all the changes within the Docker container itself by running: | ||||||
:: | ||||||
|
||||||
$ cd omero-figure | ||||||
$ docker build -t figure-devel . | ||||||
$ export OMEROHOST=demo.openmicroscopy.org | ||||||
|
||||||
$ docker run -ti -e OMEROHOST=YOUR_HOST -p 4080:4080 figure-devel | ||||||
The preferred option is to mount the repository containing the omero-figure code. You can make the changes locally and run `grunt watch` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
as described above and see changes in the docker container. To do so, run: | ||||||
:: | ||||||
|
||||||
$ cd /PATH_TO_GIT_REPO/omero-figure | ||||||
$ grunt build | ||||||
$ grunt watch # to see updates | ||||||
will-moore marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
$ docker run -ti -e OMEROHOST -p 4080:4080 -v /PATH_TO_GIT_REPO/omero-figure:/home/figure/src figure-devel | ||||||
will-moore marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
The preferred option is to mount the repository containing the omero-figure code. Make the changes locally and see the changes in the docker container. To do so, run: | ||||||
|
||||||
Alternatively, to run and develop ``omero-figure`` within the Docker container itself: | ||||||
:: | ||||||
$ docker run -ti -e OMEROHOST=YOUR_HOST -p 4080:4080 -v /PATH_TO_GIT_REPO/omero-figure:/home/figure/src figure-devel | ||||||
|
||||||
$ docker run -ti -e OMEROHOST -p 4080:4080 figure-devel | ||||||
will-moore marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
After starting the container, run ``docker ps`` in another terminal to find the ID of the container. Then run: | ||||||
|
||||||
:: | ||||||
|
||||||
$ docker exec -u 0 -it CONTAINER_ID bash # replace CONTAINER_ID by the correct value | ||||||
$ cd /home/figure/src | ||||||
$ grunt watch | ||||||
$ vi src/js/app.js | ||||||
$ grunt build # or run grunt watch in another terminal | ||||||
|
||||||
|
||||||
|
||||||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as per @jburel's comment - this works fine for me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, have to eat my words. It works fine only up to a point. This means that the docker image builds fine, and the docker starts as expected. I am able to connect to demo server. But then:
index.html
file and renaming theExport PDF
button does not appear immediately after refreshExport PDF
button manipulation in theindex.html
is immediately visible after refresh of the browserAdding
-e CONFIG_omero_web_debug=true
to thedocker run...
cmd with thelatest
build image does not help, still no changes visible after refresh. Note that the changes are visible if you stop the docker and run thedocker run...
cmd again - then it works even with thelatest
image