Deploying to gh-pages from @ 622daf4 🚀

Author: yuyuyureka

unstable/deployment/container.html

@@ -196,12 +196,12 @@ <h2 id="prequesits"><a class="header" href="#prequesits">Prequesits</a></h2>
 </li>
 </ul>
 <h2 id="fernglas-backend"><a class="header" href="#fernglas-backend">Fernglas Backend</a></h2>
-<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas:fernglas-0.2.1
+<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas:fernglas-0.2.2
 </code></pre>
 <p>You need to write a config file to specify Fernglas configuration. This needs to be put under <code>/config/config.yml</code> in the standard configuration.
 See the chapter on <a href="configuration/README.html">configuration</a> for more information on how to write the collectors configuration.</p>
 <h2 id="fernglas-frontend"><a class="header" href="#fernglas-frontend">Fernglas Frontend</a></h2>
-<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas-frontend:fernglas-0.2.1
+<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas-frontend:fernglas-0.2.2
 </code></pre>
 <p>By setting <code>serve_static: true</code> in the config, the backend will also serve the bundled frontend files from the same webserver as the API.</p>
 <p>You can take the fernglas-frontend image as base and serve the files with your own web server directly, if you want. The files need to be exposed at <code>/</code> of your domain, while the <code>/api/</code> path should be passed through to the API server.</p>

unstable/deployment/manual/backend.html

@@ -178,7 +178,7 @@ <h1 class="menu-title">Fernglas Manual</h1>
                         <h1 id="backend"><a class="header" href="#backend">Backend</a></h1>
 <p>Download the statically linked binaries and place them at <code>/usr/local/bin/</code>. Make them executable.</p>
 <pre><code>$ sudo mkdir -p /usr/local/bin
-$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.1/fernglas-static-0.2.1-x86-64-linux.tar.xz | sudo tar -C /usr/local/bin -xJ
+$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.2/fernglas-static-0.2.2-x86-64-linux.tar.xz | sudo tar -C /usr/local/bin -xJ
 </code></pre>
 <p>File: /etc/fernglas/config.yml</p>
 <pre><code class="language-yaml">api:

unstable/deployment/manual/frontend.html

@@ -180,7 +180,7 @@ <h1 id="frontend-and-reverse-proxy"><a class="header" href="#frontend-and-revers
 <p>Alternatively download the prebuilt frontend tar.
 Extract it to <code>/usr/local/share/fernglas-frontend</code>.</p>
 <pre><code>$ sudo mkdir -p /usr/local/share/fernglas-frontend
-$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.1/fernglas-frontend-0.2.1.tar.xz | sudo tar -C /usr/local/share/fernglas-frontend -xJ
+$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.2/fernglas-frontend-0.2.2.tar.xz | sudo tar -C /usr/local/share/fernglas-frontend -xJ
 </code></pre>
 <p>Set up your reverse proxy / webserver.
 A configuration for nginx might look like this:</p>

unstable/print.html

@@ -264,20 +264,20 @@ <h2 id="prequesits"><a class="header" href="#prequesits">Prequesits</a></h2>
 </li>
 </ul>
 <h2 id="fernglas-backend"><a class="header" href="#fernglas-backend">Fernglas Backend</a></h2>
-<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas:fernglas-0.2.1
+<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas:fernglas-0.2.2
 </code></pre>
 <p>You need to write a config file to specify Fernglas configuration. This needs to be put under <code>/config/config.yml</code> in the standard configuration.
 See the chapter on <a href="deployment/configuration/README.html">configuration</a> for more information on how to write the collectors configuration.</p>
 <h2 id="fernglas-frontend"><a class="header" href="#fernglas-frontend">Fernglas Frontend</a></h2>
-<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas-frontend:fernglas-0.2.1
+<pre><code class="language-sh">docker pull ghcr.io/wobcom/fernglas-frontend:fernglas-0.2.2
 </code></pre>
 <p>By setting <code>serve_static: true</code> in the config, the backend will also serve the bundled frontend files from the same webserver as the API.</p>
 <p>You can take the fernglas-frontend image as base and serve the files with your own web server directly, if you want. The files need to be exposed at <code>/</code> of your domain, while the <code>/api/</code> path should be passed through to the API server.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="manual-setup"><a class="header" href="#manual-setup">Manual Setup</a></h1>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="backend"><a class="header" href="#backend">Backend</a></h1>
 <p>Download the statically linked binaries and place them at <code>/usr/local/bin/</code>. Make them executable.</p>
 <pre><code>$ sudo mkdir -p /usr/local/bin
-$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.1/fernglas-static-0.2.1-x86-64-linux.tar.xz | sudo tar -C /usr/local/bin -xJ
+$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.2/fernglas-static-0.2.2-x86-64-linux.tar.xz | sudo tar -C /usr/local/bin -xJ
 </code></pre>
 <p>File: /etc/fernglas/config.yml</p>
 <pre><code class="language-yaml">api:
@@ -314,7 +314,7 @@ <h2 id="fernglas-frontend"><a class="header" href="#fernglas-frontend">Fernglas
 <p>Alternatively download the prebuilt frontend tar.
 Extract it to <code>/usr/local/share/fernglas-frontend</code>.</p>
 <pre><code>$ sudo mkdir -p /usr/local/share/fernglas-frontend
-$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.1/fernglas-frontend-0.2.1.tar.xz | sudo tar -C /usr/local/share/fernglas-frontend -xJ
+$ wget -O- https://github.com/wobcom/fernglas/releases/download/fernglas-0.2.2/fernglas-frontend-0.2.2.tar.xz | sudo tar -C /usr/local/share/fernglas-frontend -xJ
 </code></pre>
 <p>Set up your reverse proxy / webserver.
 A configuration for nginx might look like this:</p>