Use console for CLI examples

Amazingly the rouge highlighter used by Jekyll (kramdown) has a style
called `console` which highlights the prompt perfectly, and also help
the eye distinguish between prompt, command, and output.

The second best option is the `cisco_ios` style, and even though that
looks very good too, I don't think we want to pimp another network OS
in our own documentation.

Signed-off-by: Joachim Wiberg <[email protected]>

Author: troglobit

_posts/2024-03-08-containers.md

@@ -30,7 +30,7 @@ blog post is the first in a series of posts that aims to show this.
 All configuration and administration of networking and containers is
 done through the CLI:
 
-```
+```console
 admin@infix:~$ cli
 
 See the 'help' command for an introduction to the system
@@ -66,7 +66,7 @@ to the container as a regular interface.
 
 Here's how you create a container bridge:
 
-```
+```console
 admin@infix:/> configure
 admin@infix:/config> edit interface docker0
 admin@infix:/config/interface/docker0> set container-network
@@ -83,7 +83,7 @@ be using [docker://nginx:alpine](https://hub.docker.com/_/nginx).  It's
 a relatively small container with the Nginx web server built on top of
 the Alpine Linux image.
 
-```
+```console
 admin@infix:/> configure
 admin@infix:/config> edit container web
 admin@infix:/config/container/web/> set image docker://nginx:alpine
@@ -96,13 +96,13 @@ admin@infix:/config/container/web/network/> leave
 Issuing the command `leave` queues a job to download the image and
 create a container in the background.  To see the progress:
 
-```
+```console
 admin@infix:/> show log container
 ```
 
 or just poll the status command:
 
-```
+```console
 admin@infix:/> show container
 CONTAINER ID  IMAGE                           COMMAND               CREATED         STATUS         PORTS               NAMES
 c60a6deeea4e  docker.io/library/nginx:alpine  nginx -g daemon o...  2 minutes ago   Up 2 minutes   0.0.0.0:8080->80/tcp  web
@@ -128,7 +128,7 @@ most importantly, image upgrades.
 
 Here's how to add a volume to your container:
 
-```
+```console
 admin@infix:/> configure
 admin@infix:/config/> edit container web
 admin@infix:/config/container/web/> edit volume content
@@ -140,7 +140,7 @@ Named volumes have the downside of being opaque to the host, so the
 easiest is to upload the content using `scp` or editing it directly
 in the container:
 
-```
+```console
 admin@infix:/> container shell web
 d95ce9f7674d:/# vi /usr/share/nginx/html/
 50x.html    index.html
@@ -165,7 +165,7 @@ This feature is perfectly suited for container applications that need a
 specific site setup.  For example a configuration file.  Here we use the
 same container image to bundle an `index.html` file:
 
-```
+```console
 admin@infix:/> configure
 admin@infix:/config/> edit container web
 admin@infix:/config/container/web/> edit mount index.html
@@ -215,7 +215,7 @@ hold down Ctrl while tapping the X and C keys).
 
 Leave configuration context to activate your changes:
 
-```
+```console
 admin@infix:/config/container/web/mount/index.html/> leave
 ```
 
@@ -227,7 +227,7 @@ Reload your browser to see the change.
 That's the end of the first post about containers in Infix.  Remember to
 save your changes for next boot:
 
-```
+```console
 admin@infix:/> copy running-config startup-config
 ```
 

_posts/2024-07-24-setting-hostname.md

@@ -11,7 +11,7 @@ the hostname of a device.  The default is a unique name composed from
 the built-in default name suffixed by the last three octets of the base
 MAC address.
 
-```
+```console
 admin@infix-c0-ff-ee-:/>
 ```
 
@@ -21,7 +21,7 @@ Infix build and can be [tailored to your product][0].
 
 The hostname can be changed from the system configuration context:
 
-```
+```console
 admin@infix-c0-ff-ee:/> configure
 admin@infix-c0-ff-ee:/config/> edit system
 admin@infix-c0-ff-ee:/config/system/> set hostname example

_posts/2024-07-25-bridge-networking.md

@@ -11,7 +11,7 @@ This is an example of how to set up a VLAN transparent bridge with a
 DHCP assigned IP address.  We have a system with two interfaces, or
 ports, named `eth0` and `eth1`.
 
-```
+```console
 admin@example:/> show interfaces 
 INTERFACE       PROTOCOL   STATE       DATA
 lo              ethernet   UP          00:00:00:00:00:00
@@ -27,7 +27,7 @@ eth1            ethernet   UP          00:c0:ff:ee:00:02
 Creating a bridge and setting our interfaces as bridge ports is a
 straight forward operation.
 
-```
+```console
 admin@example:/> configure
 admin@example:/config/> set interface br0
 admin@example:/config/> set interface eth0 bridge-port bridge br0
@@ -64,7 +64,7 @@ interfaces {
 
 Now we enable a DHCP client on `br0` and activate the changes.
 
-```
+```console
 admin@example:/config/> set dhcp-client client-if br0
 admin@example:/config/> leave
 admin@example:/>
@@ -73,7 +73,7 @@ admin@example:/>
 Back in admin-exec mode we inspect the changes and notice the bridge has
 already got a DHCP lease from the server.
 
-```
+```console
 admin@example:/> show interfaces 
 INTERFACE       PROTOCOL   STATE       DATA
 lo              ethernet   UP          00:00:00:00:00:00
@@ -90,7 +90,7 @@ admin@example:/>
 
 Remember to save your changes for next boot:
 
-```
+```console
 admin@infix:/> copy running-config startup-config
 ```
 

_posts/2024-07-25-passwordless-login.md

@@ -13,7 +13,7 @@ User management is available in the system authentication configuration
 context and there is a dedicated `change` command available to simplify
 the process:
 
-```
+```console
 admin@example:/> configure
 admin@example:/config/> edit system authentication user admin
 admin@example:/config/system/authentication/user/admin/> change password
@@ -50,7 +50,7 @@ SSH key login enabled.  The following shows how to add a an authorized
 With SSH keys in place it is possible to disable password login, just
 remember to verify SSH login and network connectivity before doing so.
 
-```
+```console
 admin@example:/config/> edit system authentication user admin
 admin@example:/config/system/authentication/user/admin/> edit authorized-key jacky@host
 admin@example:/config/system/authentication/user/admin/authorized-key/jacky@host/> set algorithm ssh-rsa
@@ -78,7 +78,7 @@ of.
 To give another user administrator rights we add them to the `admin`
 group:
 
-```
+```console
 admin@example:/config/> edit nacm group admin
 admin@example:/config/nacm/group/admin/> set user-name jacky
 admin@example:/config/nacm/group/admin/> leave