switch to page bundles for pictures

content/post/2018/speedtest-plotter.md → content/post/2018/speedtest-plotter/index.md

@@ -5,6 +5,10 @@ date: 2018-09-19T20:51:03+02:00
 
 toc: true
 
+resources:
+  - name: img:counter
+    src: '**.png'
+
 tags:
   - docker
   - networks
@@ -60,7 +64,7 @@ You can find my project [on GitHub](https://github.com/ansemjo/speedtest-plotter
 
 When you think you've had enough, run `docker logs` and look at your data.
 
-![](/images/speedtest-plotter/resultscsv.png)
+![](resultscsv.png)
 
 Wonderful. What now?
 
@@ -104,17 +108,17 @@ with:
 Save your results in `results.csv` and the above script in `plotscript`. Then run
 `gnuplot ./plotscript` and you'll be rewarded with a graph:
 
-![](/images/speedtest-plotter/example.png)
+![](example.png)
 
 Leave the container running for a day, apply a different smoothing function and you'll end up with
 something that clearly shows some variation with the time of day:
 
-![](/images/speedtest-plotter/example_bezier.png)
+![](example_bezier.png)
 
 But that is still nowhere near the promised 500 Mbps? Have you tried .. you know .. turning it off
 and on again?
 
-![](/images/speedtest-plotter/restart.png)
+![](restart.png)
 
 A-ha! So a router reboot 'fixed' my slow connection? This is just the beginning of my debugging
 effort but visualizing the data definitely helped.

content/post/install-esxi-6.5-on-a-supermicro-x10sba.md → content/post/install-esxi-6.5-on-a-supermicro-x10sba/index.md

@@ -53,7 +53,7 @@ should also increase the baud rate to something sensible like 115200 in the
 advanced features of the FTDI chip in your nullmodem cable but these settings
 work great for me:
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/6.png)
+![](6.png)
 
 To connect from my laptop, I use [picocom](https://linux.die.net/man/8/picocom)
 after adding my user to the `uucp` group:
@@ -69,7 +69,7 @@ serial and reach the BIOS Setup and then disable the `Integrated Graphic Device`
 under `Advanced > Chipset Configuration > North Bridge > Graphics
 Configuration`:
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/7.png)
+![](7.png)
 
 I am actually not sure if this is required. But I disabled it and had no
 more problems during installation. And since I now had a working serial
@@ -157,7 +157,7 @@ Insert the prepared USB stick into one of the USB ports of your X10SBA and make
 sure that you are booting from it. You might need to adjust the boot order in
 your BIOS. I chose the internal USB-A header on the motherboard.
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/4.jpg)
+![](4.jpg)
 
 Since we didn't install any EFI binaries it should boot in legacy BIOS mode. But
 just make sure it does anyway because the ISO is certainly containing EFI
@@ -166,19 +166,19 @@ booting through those.
 
 You should be greeted by this screen:
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/0.png)
+![](0.png)
 
 Wait for the ISO to load and then quickly press `Tab` in the second loader to
 add additional kernel options `gdbPort=none logPort=none tty2Port=com1`:
 [reference](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-B67A3552-CECA-4BF7-9487-4F36507CD99E.html)
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/1.png)
+![](1.png)
 
 Append those options and press Enter. Nothing will happen for a few seconds
 until you'll see loaded modules rushing by and you are finally greeted by the
 VMware ESXi Installer:
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/2.png)
+![](2.png)
 
 At this point I had to disable the fullscreen shortcut key `F11` in my
 gnome-terminal settings since this key is used to accept various options in the
@@ -207,14 +207,14 @@ As far as I can tell, the default settings for both `VMkernel.Boot.logPort` and
 `VMkernel.Boot.tty2Port` to `com1`. If you want to be sure, you can set both 
 `logPort` and `gdbPort` to `none` to definitely disable them.
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/3.png)
+![](3.png)
 
 After this you can reboot. It shouldn't matter if you are booting through UEFI
 or legacy BIOS mode anymore either, since you should see output on the serial
 console as soon as the VMKernel starts initializing (which takes a little more
 than a minute in my case).
 
-![](/images/install-esxi-6.5-on-a-supermicro-x10sba/5.png)
+![](5.png)
 
 Voilà!
 

content/post/paypal-2fa-app.md → content/post/paypal-2fa-app/index.md

@@ -98,7 +98,11 @@ you could use
 The string needs to be urlencoded though, so e.g. use `%20` instead of spaces. Then
 display a QR code in your terminal with `qrencode` and scan it with your app:
 
-![](/images/paypal-2fa-app/0.png "$ qrencode -t UTF8 'otpauth://totp/PayPal:VSMT89594652?secret=GAHXEUAHO6KE63TUJGVHS53VVKHACPVN&digits=6&period=30&algorithm=sha1&issuer=Symantec'")
+```
+$ qrencode -t UTF8 'otpauth://totp/PayPal:VSMT89594652?secret=GAHXEUAHO6KE63TUJGVHS53VVKHACPVN&digits=6&period=30&algorithm=sha1&issuer=Symantec'
+```
+
+![](0.png "qrencode output of the command above")
 
 Note that using an online tool to create this QR code might not be the wisest idea. Please don't
 use this example either.