fix: syntax highlighting in posts and favicon

src/blog/config.toml

@@ -61,6 +61,6 @@ use_full_hack_font = true
 #           Mimetype defaults to "image/x-icon".
 #           The URL should point at a file located
 #           in your site's "static" directory.
-# favicon = "static/favicon.jpg"
-# favicon_mimetype = "image/jpg"
+# favicon = "static/favicon.ico"
+# favicon_mimetype = "image/vnd.microsoft.icon"
 page_titles = "combined"

src/blog/content/VPS-setup-2-electric-boogaloo.md

@@ -31,7 +31,7 @@ I decided to choose [Ubuntu Server 22.04](https://ubuntu.com/download/server) fo
 
 To clone all the repos I needed to get back up and running, I uploaded an SSH key to github to authenticate the cloning of my private repositories. There is a guide to adding SSH keys to GitHub [here](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account). You can then append the following to your `.gitconfig` file to prioritise using SSH for git actions.
 
-```shell
+```sh
 [url "git@github.com:"]
         insteadOf = https://github.com/
 [url "ssh://git@github.com:"]
@@ -41,7 +41,7 @@ To clone all the repos I needed to get back up and running, I uploaded an SSH ke
 
 There is however perhaps a more efficient way of doing this, instead of manually cloning all of your repos one by one, using the [GitHub CLI](https://cli.github.com/) and a small shell script. Once `gh` is linked to your GitHub account you can run the following script to clone every repo you own.
 
-```shell
+```sh
 gh repo list --limit num-of-repos |awk '{print $1}' | xargs -L1 gh repo clone
 ```
 

src/blog/content/automating-container-updates-with-ouroboros.md

@@ -101,7 +101,7 @@ jobs:
 
 - To run Ouroboros:
 
-```docker
+```sh
 docker run -d --name ouroboros \
   -v /var/run/docker.sock:/var/run/docker.sock \
   ghcr.io/gmt2001/ouroboros
@@ -112,7 +112,7 @@ docker run -d --name ouroboros \
   - stop the containers
   - run the snippet below, filling in the details you need to
 
-```docker
+```sh
 docker run -d \
 --name=INSERT NAME \
 -p AN-UNUSED-PORT:THE-PORT-THE-SERVICE-RUNS-ON \

src/blog/content/my-current-vps-setup.md

@@ -44,7 +44,7 @@ My Git server at https://git.crimsontome.com (as reccomended by a good friend [S
 
 https://links.crimsontome.com is created from a [littlelink](https://github.com/techno-tim/littlelink-server) container. It is an open-source self-hosted alternative to services like LinkTree. It contains links to most of my public services and is ran through this docker-compose file
 
-```dockerfile
+```yml
 version: "3.0"
 services:
   littlelink-server:
@@ -96,7 +96,7 @@ services:
 
 [Nginx Proxy Manager](https://nginxproxymanager.com/) is a project that 'comes as a pre-built docker image that enables you to easily forward to your websites running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt'
 
-```dockerfile
+```yml
 version: '3'
 services:
   app:
@@ -117,7 +117,7 @@ You can also use it to lock sites that don't come with their own authenticattion
 
 Whilst currently not fully functional, https://paste.crimsontome.com hosts my [PrivateBin](https://privatebin.info/) instance. Like most of my services it runs inside a docker container
 
-```dockerfile
+```sh
 docker run -d --restart="always" --read-only -p 8080:8080 -v $PWD/privatebin-data:/srv/data privatebin/nginx-fpm-alpine
 ```
 
@@ -125,7 +125,7 @@ docker run -d --restart="always" --read-only -p 8080:8080 -v $PWD/privatebin-dat
 
 [Dashy](https://dashy.to/) can be ran in a docker container, but some plugins _do not_ work whilst Dashy is in one, so I am using npm to build and serve it instead. Once you are done setting up dashy
 
-```shell
+```sh
 git clone https://github.com/Lissy93/dashy.git
 cd dashy
 # make your changes to public/conf

src/blog/content/on-switching-to-nginx-properly.md

@@ -62,7 +62,7 @@ Once I knew the service was running correctly, I had to verify that the default
 
 Next was adding the following to my config at `/etc/nginx/nginx.conf` within the `http` block and replacing 'port-number' with the corresponding port for that service
 
-```nginx
+```
 http {
 	# ... default config...
 	upstream service {
@@ -78,7 +78,7 @@ Upstream is nice for handling services that don't have a defined source like `/v
 
 Next was adding individual site configuration, for example my main page at `/etc/nginx/sites-enabled/crimsontome.com.conf`:
 
-```nginx
+```
 server {
     listen 80
     server_name crimsontome.com;
@@ -107,7 +107,7 @@ sudo ufw status
 
 then to give each site it's certificate
 
-```txt
+```sh
 xargs -L1 sudo certbot --nginx --expand  -d < ~/domains
 ```
 
@@ -190,7 +190,7 @@ install_letsencrypt_signed
 
 Adding this to `/etc/nginx/snippets/listen-https.conf`
 
-```nginx
+```
 listen 443 http2 ssl;
 listen [::]:443 http2 ssl;
 add_header Strict-Transport-Security "max-age=31536000" always;
@@ -200,7 +200,7 @@ ssl_certificate_key /etc/cert/private.key;
 
 and this to the default Nginx http block
 
-```nginx
+```
 # plaintext HTTP server:
 #   1) sends redirect to HTTPS servers
 #   2) serves ACME challenge for renewing SSL certificate
@@ -242,7 +242,7 @@ sudo crontab -e
 
 adding the following
 
-```txt
+```sh
 42 7 1 * * xargs update-cert < /home/ctome/domains 2>&1 > /var/log/cert.log
 ```