https://github.com/imagej/imagej-updater-tests

Docker-based test infrastructure for ImageJ Updater
https://github.com/imagej/imagej-updater-tests

docker imagej sandbox tests updater

Last synced: about 12 hours ago
JSON representation

Docker-based test infrastructure for ImageJ Updater

• Host: GitHub
• URL: https://github.com/imagej/imagej-updater-tests
• Owner: imagej
• Created: 2017-12-13T23:31:49.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2017-12-14T15:42:27.000Z (about 7 years ago)
• Last Synced: 2024-11-09T03:27:25.383Z (about 2 months ago)
• Topics: docker, imagej, sandbox, tests, updater
• Size: 3.91 KB
• Stars: 2
• Watchers: 9
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Testing ImageJ Updater

======================

[ijtest/docker-compose.yml](ijtest/docker-compose.yml) provides

a sandbox for testing ImageJ Updater behavior. This is done by

using an internal network, which permits no connections to outside

resources. Only inner container connections are possible.

The mirrored update sites created under "Setup" below are then

linked into the Docker containers with the expected alias. If

`./ImageJ-linux64 --update ...` tries to access any other URL,

there will be a short hang before a stacktrace is printed.

An ownCloud WebDav server is also started in case the client

would like to push to a clean update site.

Setup

-----

* install docker, docker-compose, etc.

* `wget --mirror update.imagej.net # 1 GB`

* `wget --mirror update.fiji.sc # 2.4 GB`

* `wget -r -np http://sites.imagej.net/Fiji-Legacy/`

* `wget --mirror sites.imagej.net/Fiji-Legacy  # 17 MB`

* Make any necessary changes to the mirrored directories.

  This does not *yet* support using the provided NGINX

  instances for uploading, though that is likely doable

  as well.

Usage

-----

 * `cd ijtest`

 * Execute: `docker-compose up --abort-on-container-exit`

   and watch the output (See [example_out.txt](example_out.txt))

 * Make changes to the `command:` element for the client

   container to see different behavior *or* change the command

   to `bash` for interacting with the container. Use:

   `docker-compose exec client bash` to enter the started

   container.