Website build Website/master-52
diff --git a/README.md b/README.md
index 43cc2b6..bc57d66 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,9 @@
Serve Homepage:
JEKYLL_VERSION=4
- docker run --rm --volume="$PWD:/srv/jekyll:z" --volume="$PWD/vendor/bundle:/usr/local/bundle:z" -eJEKYLL_UID=$UID -p 4000:4000 -it jekyll/jekyll:$JEKYLL_VERSION jekyll serve
+ docker run --rm --volume="$PWD:/srv/jekyll:z" --volume="$PWD/vendor/bundle:/usr/local/bundle:z" -eJEKYLL_UID=$UID -p 4000:4000 -it docker.io/jekyll/jekyll:$JEKYLL_VERSION jekyll serve
On Windows:
set JEKYLL_VERSION=4
- docker run --rm --volume="%CD%:/srv/jekyll" --volume="%CD%/vendor/bundle:/usr/local/bundle" -p 4000:4000 -it jekyll/jekyll:%JEKYLL_VERSION% jekyll serve
+ docker run --rm --volume="%CD%:/srv/jekyll" --volume="%CD%/vendor/bundle:/usr/local/bundle" -p 4000:4000 -it docker.io/jekyll/jekyll:%JEKYLL_VERSION% jekyll serve
diff --git a/contribute/index.html b/contribute/index.html
index 54dd9af..5a6ed38 100644
--- a/contribute/index.html
+++ b/contribute/index.html
@@ -136,7 +136,7 @@
<li>contain a README covering a basic introduction and the idea behind the package,</li>
<li>include the Helm charts constituting the components of the package,</li>
<li>provide some guidance regarding what users might want to do with the package after installation.</li>
- <li>include the <code class="highlighter-rouge">iot-package</code> key word in their <em>Chart.yaml</em></li>
+ <li>include the <code class="language-plaintext highlighter-rouge">iot-package</code> key word in their <em>Chart.yaml</em></li>
</ul>
</li>
</ul>
@@ -150,9 +150,9 @@
as well as packages that are comprised of multiple projects:</p>
<ul>
- <li>The <code class="highlighter-rouge">charts</code> folder contains Helm charts for Eclipse IoT projects. Each sub-folder contains a chart for
+ <li>The <code class="language-plaintext highlighter-rouge">charts</code> folder contains Helm charts for Eclipse IoT projects. Each sub-folder contains a chart for
one project.</li>
- <li>The <code class="highlighter-rouge">packages</code> folder contains the IoT packages. Each sub-folder represents one package.</li>
+ <li>The <code class="language-plaintext highlighter-rouge">packages</code> folder contains the IoT packages. Each sub-folder represents one package.</li>
</ul>
<h2 id="requirements-for-charts">Requirements for charts</h2>
@@ -165,8 +165,8 @@
<ul>
<li>must not contain other charts that they depend on</li>
- <li>must pass the Helm linter (<code class="highlighter-rouge">helm lint</code>)</li>
- <li>must successfully launch with default values (<code class="highlighter-rouge">helm install .</code>)
+ <li>must pass the Helm linter (<code class="language-plaintext highlighter-rouge">helm lint</code>)</li>
+ <li>must successfully launch with default values (<code class="language-plaintext highlighter-rouge">helm install .</code>)
<ul>
<li>all pods go to the running state (or NOTES.txt provides further instructions if a required value is missing e.g. <a href="https://github.com/helm/charts/blob/master/stable/minecraft/templates/NOTES.txt#L3">minecraft</a>)</li>
<li>all services have at least one endpoint</li>
@@ -201,21 +201,21 @@
<p>Helm charts</p>
<ul>
- <li>must include a <code class="highlighter-rouge">README.md</code>, containing:
+ <li>must include a <code class="language-plaintext highlighter-rouge">README.md</code>, containing:
<ul>
<li>a short description of the chart</li>
<li>any prerequisites or requirements</li>
</ul>
</li>
- <li>must include a short <code class="highlighter-rouge">NOTES.txt</code>, containing:
+ <li>must include a short <code class="language-plaintext highlighter-rouge">NOTES.txt</code>, containing:
<ul>
<li>any relevant post-installation information for the chart</li>
<li>instructions on how to access the application or service provided by the chart</li>
</ul>
</li>
- <li>must contain a <code class="highlighter-rouge">values.yaml</code> file which contains a reasonable default configuration and explains
+ <li>must contain a <code class="language-plaintext highlighter-rouge">values.yaml</code> file which contains a reasonable default configuration and explains
how the properties can be used to customize the chart</li>
- <li>must include the <code class="highlighter-rouge">iot-chart</code> key word in their <em>Chart.yaml</em></li>
+ <li>must include the <code class="language-plaintext highlighter-rouge">iot-chart</code> key word in their <em>Chart.yaml</em></li>
</ul>
<h2 id="merge-approval-and-release-process">Merge approval and release process</h2>
@@ -241,7 +241,7 @@
</thead>
<tbody>
<tr>
- <td>Update the <code class="highlighter-rouge">README.md</code> file</td>
+ <td>Update the <code class="language-plaintext highlighter-rouge">README.md</code> file</td>
<td>patch version</td>
</tr>
<tr>
diff --git a/faq/index.html b/faq/index.html
index b612091..24cc3ee 100644
--- a/faq/index.html
+++ b/faq/index.html
@@ -155,17 +155,17 @@
</section>
<section>
- <h3 id="why-are-you-using-insecure-settings">Why are you using insecure settings?</h3><p>Every now and then, you might spot a <code class="highlighter-rouge">--insecure</code> (or equivalent settings)
+ <h3 id="why-are-you-using-insecure-settings">Why are you using insecure settings?</h3><p>Every now and then, you might spot a <code class="language-plaintext highlighter-rouge">--insecure</code> (or equivalent settings)
in the commands.</p>
<p>It is unfortunate, but sometimes it is necessary. With the availability of
<a href="https://letsencryt.org">Let’s Encrypt</a>, it would actually be rather simple
-to add proper TLS certificates. But when you are running a local <code class="highlighter-rouge">minikube</code>
+to add proper TLS certificates. But when you are running a local <code class="language-plaintext highlighter-rouge">minikube</code>
instance, you can’t properly use certificates. Also does the process of getting
a proper Let’s Encrypt certificate still need a significant effort and understanding,
on the user side, especially when requesting a wildcard certificate.</p>
-<p>You are encouraged to try with a proper certificate though, and drop the <code class="highlighter-rouge">--insecure</code>
+<p>You are encouraged to try with a proper certificate though, and drop the <code class="language-plaintext highlighter-rouge">--insecure</code>
for commands.</p>
</section>
diff --git a/packages/cloud2edge/installation/index.html b/packages/cloud2edge/installation/index.html
index b60fb79..bdb0cde 100644
--- a/packages/cloud2edge/installation/index.html
+++ b/packages/cloud2edge/installation/index.html
@@ -83,7 +83,7 @@
<div class="col-12 col-md-8 col-lg-9">
- <p>You will need a Kubernetes instance, the <code class="highlighter-rouge">kubectl</code> and the <code class="highlighter-rouge">helm</code> tool in order to deploy this package.
+ <p>You will need a Kubernetes instance, the <code class="language-plaintext highlighter-rouge">kubectl</code> and the <code class="language-plaintext highlighter-rouge">helm</code> tool in order to deploy this package.
Please refer to our <a href="/packages/prereqs">pre-requisites</a> page for details.
Any Kubernetes compatible cluster will do, as long as it meets the requirements.</p>
@@ -96,7 +96,7 @@
<p>This should print out the version of the client, but must also print out the version of the server.</p>
<p><details><summary>Example output</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T17:01:15Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.1", GitCommit:"d647ddbd755faf07169599a625faf302ffc34458", GitTreeState:"clean", BuildDate:"2019-10-02T17:01:15Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c2a5caf", GitCommit:"c2a5caf", GitTreeState:"clean", BuildDate:"2019-09-21T02:12:52Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div> </div>
</div></details></p>
@@ -105,7 +105,7 @@
<p>The Cloud2Edge package consists of multiple components. In order to keep them together and separate
from other components running in your Kubernetes cluster, it is feasible to install them into
-their own name space. The following command creates the <code class="highlighter-rouge">cloud2edge</code> name space but you can select any
+their own name space. The following command creates the <code class="language-plaintext highlighter-rouge">cloud2edge</code> name space but you can select any
other name as well.</p>
<div class="clipboard"><pre><code>NS=cloud2edge
diff --git a/packages/cloud2edge/tour/index.html b/packages/cloud2edge/tour/index.html
index 95351bb..92960ae 100644
--- a/packages/cloud2edge/tour/index.html
+++ b/packages/cloud2edge/tour/index.html
@@ -161,7 +161,7 @@
"water-amount": "3liters"
}' http://$DITTO_API_IP:$DITTO_API_PORT_HTTP/api/2/things/org.eclipse.packages.c2e:demo-device/inbox/messages/start-watering?timeout=0</code></pre></div>
- <p>Specifying the <code class="highlighter-rouge">timeout=0</code> parameter indicates that the HTTP request will directly be accepted and Ditto does not wait
+ <p>Specifying the <code class="language-plaintext highlighter-rouge">timeout=0</code> parameter indicates that the HTTP request will directly be accepted and Ditto does not wait
for a response.</p>
<p>If Ditto shall wait for a response, responding with the response from the device at the HTTP level, simply increase the
@@ -173,7 +173,7 @@
<h3 id="receiving-a-command-at-the-device">Receiving a command at the device</h3>
- <p>The device may receive a command by specifying a <code class="highlighter-rouge">ttd</code> when e.g. sending telemetry via HTTP to Hono:</p>
+ <p>The device may receive a command by specifying a <code class="language-plaintext highlighter-rouge">ttd</code> when e.g. sending telemetry via HTTP to Hono:</p>
<div class="clipboard"><pre><code>curl -i -u demo-device@org.eclipse.packages.c2e:demo-secret -H 'hono-ttd: 50' -H 'application/json' -w '\n' --data '{
"topic": "org.eclipse.packages.c2e/demo-device/things/twin/commands/modify",
@@ -186,7 +186,7 @@
command) is:</p>
<p><details><summary>Example of a received command at the device</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 200 OK
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 200 OK
hono-command: start-watering
hono-cmd-req-id: 024d84b1ceb-797b-45f5-bc87-78e9b5396645replies
content-type: application/json
@@ -202,10 +202,10 @@
<p>The response has to be correlated twice:</p>
<ul>
- <li>once for Hono in the URL: please replace the placeholder <code class="highlighter-rouge">insert-hono-cmd-req-id-here</code> with the <code class="highlighter-rouge">hono-cmd-req-id</code>
+ <li>once for Hono in the URL: please replace the placeholder <code class="language-plaintext highlighter-rouge">insert-hono-cmd-req-id-here</code> with the <code class="language-plaintext highlighter-rouge">hono-cmd-req-id</code>
HTTP header value from the received command.</li>
- <li>once for Ditto in the Ditto Protocol payload: please replace the placeholder <code class="highlighter-rouge">insert-ditto-correlation-id-header-here</code>
-with the <code class="highlighter-rouge">"correlation-id"</code> value from the received Ditto Protocol message’s <code class="highlighter-rouge">"headers"</code> object.</li>
+ <li>once for Ditto in the Ditto Protocol payload: please replace the placeholder <code class="language-plaintext highlighter-rouge">insert-ditto-correlation-id-header-here</code>
+with the <code class="language-plaintext highlighter-rouge">"correlation-id"</code> value from the received Ditto Protocol message’s <code class="language-plaintext highlighter-rouge">"headers"</code> object.</li>
</ul>
<div class="clipboard"><pre><code>curl -i -X PUT -u demo-device@org.eclipse.packages.c2e:demo-secret -H "content-type: application/json" --data-binary '{
@@ -222,10 +222,10 @@
}' http://${HTTP_ADAPTER_IP}:${HTTP_ADAPTER_PORT_HTTP}/command/res/org.eclipse.packages.c2e/org.eclipse.packages.c2e:demo-device/insert-hono-cmd-req-id-here?hono-cmd-status=200</code></pre></div>
<p>An example message response (omitting some additional HTTP headers) at the Ditto twin which waited for the command
- e.g. with a <code class="highlighter-rouge">timeout=60</code> is:</p>
+ e.g. with a <code class="language-plaintext highlighter-rouge">timeout=60</code> is:</p>
<p><details><summary>Example of a twin message response</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 200 OK
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 26
correlation-id: 715cb667-7750-4451-969e-6f8c735129ef
@@ -240,18 +240,18 @@
<p>In order to <em>link</em> Hono devices to Ditto digital twins (a.k.a. things), it is assumed that Hono device and Ditto thing
always have the same id, starting with a namespace (e.g. in reverse domain notation), followed by a colon and a name,
-e.g.: <code class="highlighter-rouge">org.acme:my-device</code>.</p>
+e.g.: <code class="language-plaintext highlighter-rouge">org.acme:my-device</code>.</p>
<h3 id="create-a-new-tenant">Create a new tenant</h3>
- <p>Create a new tenant named <code class="highlighter-rouge">my-tenant</code> in Hono:</p>
+ <p>Create a new tenant named <code class="language-plaintext highlighter-rouge">my-tenant</code> in Hono:</p>
<div class="clipboard"><pre><code>curl -i -X POST http://${REGISTRY_IP}:${REGISTRY_PORT_HTTP}/v1/tenants/my-tenant</code></pre></div>
- <p>This should return a result of <code class="highlighter-rouge">201 Created</code>.</p>
+ <p>This should return a result of <code class="language-plaintext highlighter-rouge">201 Created</code>.</p>
<p><details><summary>Example of a successful result</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 201 Created
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 201 Created
etag: be547a07-4a03-4c43-a274-d02f63f8d467
location: /v1/tenants/my-tenant
content-type: application/json; charset=utf-8
@@ -263,14 +263,14 @@
<h3 id="register-a-new-device">Register a new device</h3>
- <p>Next we can register a new device, named <code class="highlighter-rouge">org.acme:my-device-1</code> for the tenant we just created:</p>
+ <p>Next we can register a new device, named <code class="language-plaintext highlighter-rouge">org.acme:my-device-1</code> for the tenant we just created:</p>
<div class="clipboard"><pre><code>curl -i -X POST http://${REGISTRY_IP}:${REGISTRY_PORT_HTTP}/v1/devices/my-tenant/org.acme:my-device-1</code></pre></div>
- <p>This should return a result of <code class="highlighter-rouge">201 Created</code>.</p>
+ <p>This should return a result of <code class="language-plaintext highlighter-rouge">201 Created</code>.</p>
<p><details><summary>Example of a successful result</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 201 Created
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 201 Created
etag: d48f4e13-b398-4c73-bbc3-5ac97a81b3e8
location: /v1/devices/iot/org.acme:my-device-1
content-type: application/json; charset=utf-8
@@ -297,19 +297,19 @@
}]' http://${REGISTRY_IP}:${REGISTRY_PORT_HTTP}/v1/credentials/my-tenant/org.acme:my-device-1</code></pre></div>
<p><details><summary>Example of a successful result</summary><div>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 204 No Content
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>HTTP/1.1 204 No Content
etag: a7edc4b8-701a-4fe1-85c4-1717c0d24562
</code></pre></div> </div>
</div></details></p>
<h4 id="understanding-identities">Understanding identities</h4>
- <p>The previous step assigned the credentials of <code class="highlighter-rouge">my-auth-id-1</code> and <code class="highlighter-rouge">my-password</code> to the device <code class="highlighter-rouge">org.acme:my-device-1</code>.</p>
+ <p>The previous step assigned the credentials of <code class="language-plaintext highlighter-rouge">my-auth-id-1</code> and <code class="language-plaintext highlighter-rouge">my-password</code> to the device <code class="language-plaintext highlighter-rouge">org.acme:my-device-1</code>.</p>
- <p>Please note that there is a difference between the <em>username</em> of the device (<code class="highlighter-rouge">my-auth-id-1</code>) and
-the name of the device (<code class="highlighter-rouge">org.acme:my-device-1</code>). When connecting to e.g. the MQTT protocol adapter,
-you will need to use the fully qualified username of <code class="highlighter-rouge">my-auth-id-1@my-tenant</code>
-(<em>authentication id</em> and <em>tenant name</em>), rather than just the <em>device id</em> (<code class="highlighter-rouge">org.acme:my-device-1</code>).</p>
+ <p>Please note that there is a difference between the <em>username</em> of the device (<code class="language-plaintext highlighter-rouge">my-auth-id-1</code>) and
+the name of the device (<code class="language-plaintext highlighter-rouge">org.acme:my-device-1</code>). When connecting to e.g. the MQTT protocol adapter,
+you will need to use the fully qualified username of <code class="language-plaintext highlighter-rouge">my-auth-id-1@my-tenant</code>
+(<em>authentication id</em> and <em>tenant name</em>), rather than just the <em>device id</em> (<code class="language-plaintext highlighter-rouge">org.acme:my-device-1</code>).</p>
<p>The <em>authentication id</em> is only used for the authentication process. Later on, the messages will be marked
with the <em>device id</em> and the back end system isn’t aware of the <em>authentication id</em> anymore.</p>
@@ -321,13 +321,13 @@
<p>In order to create digital twins in Ditto for a newly added Hono tenant, a new connection has to be created.</p>
- <p>The <code class="highlighter-rouge">NS</code> and <code class="highlighter-rouge">RELEASE</code> variables must still be set to the value you chose during the <a href="../installation/#install-the-package">installation</a>.
+ <p>The <code class="language-plaintext highlighter-rouge">NS</code> and <code class="language-plaintext highlighter-rouge">RELEASE</code> variables must still be set to the value you chose during the <a href="../installation/#install-the-package">installation</a>.
The documented defaults are:</p>
<div class="clipboard"><pre><code>NS=cloud2edge
RELEASE=c2e</code></pre></div>
<p>Please also configure your chosen Hono tenant name <a href="#create-a-new-tenant">when your created a new tenant</a> and extract
-the Ditto devops password via <code class="highlighter-rouge">kubectl</code>:</p>
+the Ditto devops password via <code class="language-plaintext highlighter-rouge">kubectl</code>:</p>
<div class="clipboard"><pre><code>HONO_TENANT=my-tenant
DITTO_DEVOPS_PWD=$(kubectl --namespace ${NS} get secret ${RELEASE}-ditto-gateway-secret -o jsonpath="{.data.devops-password}" | base64 --decode)</code></pre></div>
@@ -427,7 +427,7 @@
<h4 id="setup-a-common-policy">Setup a common policy</h4>
<p>In order to define common authorization information for all digital twins about to be created in Ditto, we first create
-a policy with the id <code class="highlighter-rouge">org.acme:my-policy</code>:</p>
+a policy with the id <code class="language-plaintext highlighter-rouge">org.acme:my-policy</code>:</p>
<div class="clipboard"><pre><code>curl -i -X PUT -u ditto:ditto -H 'Content-Type: application/json' --data '{
"entries": {
@@ -472,7 +472,7 @@
}
}' http://${DITTO_API_IP}:${DITTO_API_PORT_HTTP}/api/2/policies/org.acme:my-policy</code></pre></div>
- <p>This should return a result of <code class="highlighter-rouge">201 Created</code> containing as response body of the created policy JSON.</p>
+ <p>This should return a result of <code class="language-plaintext highlighter-rouge">201 Created</code> containing as response body of the created policy JSON.</p>
<p>The created policy may be used for just one digital twin or for many of them. Modifying it will adjust the authorization
configuration of all twins referencing this <em>policy id</em>.</p>
@@ -480,7 +480,7 @@
<h4 id="create-the-twin">Create the twin</h4>
<p>In order to create a digital twin in Ditto, we use the same <em>device id</em> already used for creating the device at Hono as
-<em>thing id</em>: <code class="highlighter-rouge">org.acme:my-device-1</code>.<br />
+<em>thing id</em>: <code class="language-plaintext highlighter-rouge">org.acme:my-device-1</code>.<br />
Furthermore, we add a reference to the in the previous step created <em>policy id</em> in order to define the authorization
information of the twin:</p>
@@ -503,7 +503,7 @@
}
}' http://${DITTO_API_IP}:${DITTO_API_PORT_HTTP}/api/2/things/org.acme:my-device-1</code></pre></div>
- <p>This should return a result of <code class="highlighter-rouge">201 Created</code> containing as response body of the created thing JSON.</p>
+ <p>This should return a result of <code class="language-plaintext highlighter-rouge">201 Created</code> containing as response body of the created thing JSON.</p>
<p>In order to add more twins, we simply create additional devices via <a href="#register-a-new-device">“Register a new device”</a>
and add twins for them with the above snippet by simply adjusting the <em>device id</em> and <em>thing id</em> in the URL of both
diff --git a/prereqs/index.html b/prereqs/index.html
index 138d723..d8f3114 100644
--- a/prereqs/index.html
+++ b/prereqs/index.html
@@ -87,10 +87,10 @@
<h2 id="kubernetes-client">Kubernetes Client</h2>
- <p>First of all, you will need a command tool named <code class="highlighter-rouge">kubectl</code>. This application allows you to interact with
+ <p>First of all, you will need a command tool named <code class="language-plaintext highlighter-rouge">kubectl</code>. This application allows you to interact with
your Kubernetes cluster from the command line. While Kubernetes also comes with a Web UI, it is much simpler
to document the installation procedures using command line tool. Also does the Web UI change over time, and
-with different Kubernetes variants. However the <code class="highlighter-rouge">kubectl</code> tool works with all variations of Kubernetes, as it
+with different Kubernetes variants. However the <code class="language-plaintext highlighter-rouge">kubectl</code> tool works with all variations of Kubernetes, as it
uses the standardized API in the background.</p>
<p>You can find more information in the Kubernetes documentation: <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/">Install and Set Up kubectl</a>.</p>
@@ -196,7 +196,7 @@
<div class="clipboard"><pre><code>minikube start</code></pre></div>
- <p>And you can switch <code class="highlighter-rouge">kubectl</code> to the context <code class="highlighter-rouge">minikube</code>, and interact with your cluster:</p>
+ <p>And you can switch <code class="language-plaintext highlighter-rouge">kubectl</code> to the context <code class="language-plaintext highlighter-rouge">minikube</code>, and interact with your cluster:</p>
<div class="clipboard"><pre><code>kubectl config use-context minikube</code></pre></div>
@@ -206,7 +206,7 @@
<p>Which should show a proper version for the client <strong>and</strong> the server:</p>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Client Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2018-10-10T16:38:01Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Client Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2018-10-10T16:38:01Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c2a5caf", GitCommit:"c2a5caf", GitTreeState:"clean", BuildDate:"2019-09-21T02:12:52Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div> </div>
@@ -227,9 +227,9 @@
<h4 id="resources">Resources</h4>
- <p>You can translate the package resources requirements into arguments for the <code class="highlighter-rouge">start</code> command like this:</p>
+ <p>You can translate the package resources requirements into arguments for the <code class="language-plaintext highlighter-rouge">start</code> command like this:</p>
- <div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>minikube start --cpus <cpus> --disk-size <size> --memory <memory> --kubernetes-version <version>
+ <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>minikube start --cpus <cpus> --disk-size <size> --memory <memory> --kubernetes-version <version>
</code></pre></div> </div>
<p>Using the following arguments:</p>
@@ -297,11 +297,11 @@
<h3 id="curl">curl</h3>
- <p>For downloading files and execution API call the tool <code class="highlighter-rouge">curl</code> will be used.</p>
+ <p>For downloading files and execution API call the tool <code class="language-plaintext highlighter-rouge">curl</code> will be used.</p>
<h3 id="mosquitto-cli">Mosquitto CLI</h3>
- <p>Mosquitto command line tools: e.g. <code class="highlighter-rouge">moquitto_pub</code></p>
+ <p>Mosquitto command line tools: e.g. <code class="language-plaintext highlighter-rouge">moquitto_pub</code></p>
</div>
diff --git a/repository/index.html b/repository/index.html
index 60c01da..d82fd3a 100644
--- a/repository/index.html
+++ b/repository/index.html
@@ -94,9 +94,9 @@
<div class="clipboard"><pre><code>helm repo add eclipse-iot https://eclipse.org/packages/charts</code></pre></div>
-<p>This will add the repository, using the name <code class="highlighter-rouge">eclipse-iot</code>. Of course you may choose
+<p>This will add the repository, using the name <code class="language-plaintext highlighter-rouge">eclipse-iot</code>. Of course you may choose
a different name here. Just take extra care when working through tutorials, as they will
-expect the name to be <code class="highlighter-rouge">eclipse-iot</code>.</p>
+expect the name to be <code class="language-plaintext highlighter-rouge">eclipse-iot</code>.</p>
<p>After you have added the repository you should tell helm to download the index for its contents:</p>
@@ -125,7 +125,7 @@
<p>All chart changes will be verified by a <a href="https://github.com/eclipse/packages/actions">Github action</a>, this is done on every pull request.</p>
<p>Once a pull request is merged, the updated chart will be deployed by a <a href="https://ci.eclipse.org/packages/job/Website/job/master/">Jenkins job</a>.
-This job takes care of publishing the resources and generating an updated <code class="highlighter-rouge">index.yaml</code>.</p>
+This job takes care of publishing the resources and generating an updated <code class="language-plaintext highlighter-rouge">index.yaml</code>.</p>
</div>
