Automated deployment: Mon Apr 8 09:40:46 UTC 2024 9bd6b7a

getting_started/installation_options.html

@@ -249,11 +249,11 @@ <h3 id="check-that-your-system-is-suitable"><a class="header" href="#check-that-
 <pre><code>ldd --version
 </code></pre>
 <h3 id="download-the-latest-quick-start-release-bundle"><a class="header" href="#download-the-latest-quick-start-release-bundle">Download the Latest Quick-Start Release Bundle</a></h3>
-<p>Run the following command to download and unpack the <code>quickstart-1.3.0-linux-x86_64</code> folder.</p>
-<pre><code>curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.3.0/quickstart-1.3.0-linux-x86_64.tar.gz | tar xz
+<p>Run the following command to download and unpack the <code>quickstart-1.4.0-linux-x86_64</code> folder.</p>
+<pre><code>curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.4.0/quickstart-1.4.0-linux-x86_64.tar.gz | tar xz
 </code></pre>
 <p>The resulting directory contains the following structure</p>
-<pre><code>quickstart-1.3.0-linux-x86_64
+<pre><code>quickstart-1.4.0-linux-x86_64
 ├── bin
 │   ├── parsec                 # The parsec binary
 │   └── parsec-tool            # The parsec client tool
@@ -263,9 +263,9 @@ <h3 id="download-the-latest-quick-start-release-bundle"><a class="header" href="
     ├── config.toml            # The config file used by parsec
     └── parsec-cli-tests.sh    # Standard parsec-tool tests
 </code></pre>
-<p>The following examples assume you've navigated to the <code>quickstart-1.3.0-linux-x86_64/quickstart</code>
+<p>The following examples assume you've navigated to the <code>quickstart-1.4.0-linux-x86_64/quickstart</code>
 directory, so let's do that now.</p>
-<pre><code>cd quickstart-1.3.0-linux-x86_64/quickstart
+<pre><code>cd quickstart-1.4.0-linux-x86_64/quickstart
 </code></pre>
 <h3 id="configure-your-environment"><a class="header" href="#configure-your-environment">Configure Your Environment</a></h3>
 <p>Calls to the <code>parsec-tool</code> assume that the environment variable <code>PARSEC_SERVICE_ENDPOINT</code> has been
@@ -319,7 +319,7 @@ <h3 id="running-the-test-script"><a class="header" href="#running-the-test-scrip
 </code></pre>
 <p>If parsec-tool is not installed into a directory included in <code>PATH</code>, then you also need to define
 the <code>PARSEC_TOOL</code> environment variable with a full path to it. Assuming the current working
-directory is <code>quickstart-1.3.0-linux-x86_64/quickstart</code>:</p>
+directory is <code>quickstart-1.4.0-linux-x86_64/quickstart</code>:</p>
 <pre><code>export PARSEC_TOOL="$(pwd)/../bin/parsec-tool"
 </code></pre>
 <p>To run the script from the same directory, simply execute it without any arguments as follows:</p>

parsec_service/build_run.html

@@ -199,7 +199,7 @@ <h2 id="building-parsec"><a class="header" href="#building-parsec">Building Pars
 Parsec from the current directory, have the key information mappings in <code>./mappings</code> and the socket
 at <code>/tmp/parsec.sock</code>. The test configuration will make those choices.</p>
 <p>Clone the Parsec service repo,</p>
-<pre><code>git clone --branch 1.3.0 https://github.com/parallaxsecond/parsec.git
+<pre><code>git clone --branch 1.4.0 https://github.com/parallaxsecond/parsec.git
 </code></pre>
 <p>Having cloned the Parsec repository, to build and run from source using the Mbed Crypto provider and
 the test configuration:</p>

print.html

@@ -485,11 +485,11 @@ <h3 id="check-that-your-system-is-suitable"><a class="header" href="#check-that-
 <pre><code>ldd --version
 </code></pre>
 <h3 id="download-the-latest-quick-start-release-bundle"><a class="header" href="#download-the-latest-quick-start-release-bundle">Download the Latest Quick-Start Release Bundle</a></h3>
-<p>Run the following command to download and unpack the <code>quickstart-1.3.0-linux-x86_64</code> folder.</p>
-<pre><code>curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.3.0/quickstart-1.3.0-linux-x86_64.tar.gz | tar xz
+<p>Run the following command to download and unpack the <code>quickstart-1.4.0-linux-x86_64</code> folder.</p>
+<pre><code>curl -s -N -L https://github.com/parallaxsecond/parsec/releases/download/1.4.0/quickstart-1.4.0-linux-x86_64.tar.gz | tar xz
 </code></pre>
 <p>The resulting directory contains the following structure</p>
-<pre><code>quickstart-1.3.0-linux-x86_64
+<pre><code>quickstart-1.4.0-linux-x86_64
 ├── bin
 │   ├── parsec                 # The parsec binary
 │   └── parsec-tool            # The parsec client tool
@@ -499,9 +499,9 @@ <h3 id="download-the-latest-quick-start-release-bundle"><a class="header" href="
     ├── config.toml            # The config file used by parsec
     └── parsec-cli-tests.sh    # Standard parsec-tool tests
 </code></pre>
-<p>The following examples assume you've navigated to the <code>quickstart-1.3.0-linux-x86_64/quickstart</code>
+<p>The following examples assume you've navigated to the <code>quickstart-1.4.0-linux-x86_64/quickstart</code>
 directory, so let's do that now.</p>
-<pre><code>cd quickstart-1.3.0-linux-x86_64/quickstart
+<pre><code>cd quickstart-1.4.0-linux-x86_64/quickstart
 </code></pre>
 <h3 id="configure-your-environment"><a class="header" href="#configure-your-environment">Configure Your Environment</a></h3>
 <p>Calls to the <code>parsec-tool</code> assume that the environment variable <code>PARSEC_SERVICE_ENDPOINT</code> has been
@@ -555,7 +555,7 @@ <h3 id="running-the-test-script"><a class="header" href="#running-the-test-scrip
 </code></pre>
 <p>If parsec-tool is not installed into a directory included in <code>PATH</code>, then you also need to define
 the <code>PARSEC_TOOL</code> environment variable with a full path to it. Assuming the current working
-directory is <code>quickstart-1.3.0-linux-x86_64/quickstart</code>:</p>
+directory is <code>quickstart-1.4.0-linux-x86_64/quickstart</code>:</p>
 <pre><code>export PARSEC_TOOL="$(pwd)/../bin/parsec-tool"
 </code></pre>
 <p>To run the script from the same directory, simply execute it without any arguments as follows:</p>
@@ -4027,7 +4027,7 @@ <h2 id="building-parsec"><a class="header" href="#building-parsec">Building Pars
 Parsec from the current directory, have the key information mappings in <code>./mappings</code> and the socket
 at <code>/tmp/parsec.sock</code>. The test configuration will make those choices.</p>
 <p>Clone the Parsec service repo,</p>
-<pre><code>git clone --branch 1.3.0 https://github.com/parallaxsecond/parsec.git
+<pre><code>git clone --branch 1.4.0 https://github.com/parallaxsecond/parsec.git
 </code></pre>
 <p>Having cloned the Parsec repository, to build and run from source using the Mbed Crypto provider and
 the test configuration:</p>