Commit 9bc9210b authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Updated the README for small changes in Docker image

parent fc5721c544de
# Heptapod automated functional tests
WARNING: don't try and run these on anything but a throwable development
## Installation
### Client-side install
......@@ -29,18 +32,21 @@ This will test the current state of your Heptapod container.
### Choosing the version to test
By default, the `Dockerfile` from `omnibus/heptapod_docker` is loaded with
the head of the `heptapod` branch from ``.
The versions installed in the Docker image you're using are specified by the
[heptapod_revisions.json]( file.
To test your local heptapod clone:
To test your local clone of heptapod/heptapod:
- mount your local `heptapod` clone in the container (assuming below it's seen
as `/home/heptapod` from the container)
as `/home/heptapod-rails` from the container)
- execute the following in the container:
cd /var/opt/gitlab/embedded/service/gitlab-rails
hg pull /home/heptapod
hg rev -r WISHED_REVISION app lib
hg pull --config phases.publish=False /home/heptapod-rails
gitlab-ctl restart unicorn
If you want to try changes to other components (e.g., `hg-git`), do something similar.
The paths can be seen in the Docker build logs, or you can read them in the [install script](
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment