From 5f198d61d899d1e1b232e5211bc4a60f009dfd69 Mon Sep 17 00:00:00 2001 From: Pierre Chanson Date: Fri, 24 Jan 2020 11:58:30 +0100 Subject: [PATCH] update version referenced in doc --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f345747..40b56c6 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ Quick start ----------- SnapDump is available as docker application for easy deployment. Let's pull a stable version of the SnapDump server (check DockerHub to be up to date): - $ docker pull zweidenker/snap-dump:0.5.1.1 + $ docker pull zweidenker/snap-dump:0.7 To keep the snapshots on server restart we need to create a volume where snapshots can be stored. You do this by invoking: @@ -23,7 +23,7 @@ To keep the snapshots on server restart we need to create a volume where snapsho SnapDump uses internally the port 5555 for the server. This can be mapped to a local port on the host by specifying on the docker commandline. To start the server with that port and the former created volume invoke: - $ docker run -p 8888:5555 -v SnapDump:/snapshots zweidenker/snap-dump:0.5.1.1 + $ docker run -p 8888:5555 -v SnapDump:/snapshots zweidenker/snap-dump:0.7 Now our SnapDump server is up and running, we would like to first: report exceptions from a SnapDump handler image , and second: retrieve our reported exceptions on a SnapDump client image. @@ -37,7 +37,7 @@ To download a pharo image from command line you can use: To install SnapDump open a playground and execute: Metacello new - repository: 'github://zweidenker/SnapDump:0.5.1.1'; + repository: 'github://zweidenker/SnapDump:0.7'; baseline: #SnapDump; load @@ -47,7 +47,7 @@ To configure Snapdump on the handler image execute: SnapDump hackUIManager; beHandler. SnapDump uri: 'http://localhost:8888/api'. - SnapDump current projectName: 'projectname1' versionString: '1.0'. + SnapDump current projectName: 'projectname1' versionString: '0.7'. This could be executed systematically when the image is deployed and starts.