add alert blockquote styleing

BinaryPatrick · BinaryPatrick · commit e03642291355 · 2026-02-28T11:31:53.000-05:00
diff --git a/astro.config.ts b/astro.config.ts
@@ -1,4 +1,5 @@
 import { defineConfig, envField, fontProviders } from "astro/config";
+import { remarkAlert } from "remark-github-blockquote-alert";
 import tailwindcss from "@tailwindcss/vite";
 import sitemap from "@astrojs/sitemap";
 import remarkToc from "remark-toc";
@@ -20,7 +21,7 @@ export default defineConfig({
     }),
   ],
   markdown: {
-    remarkPlugins: [remarkToc, [remarkCollapse, { test: "Table of contents" }]],
+    remarkPlugins: [remarkAlert, remarkToc, [remarkCollapse, { test: "Table of contents" }]],
     shikiConfig: {
       // For more themes, visit https://shiki.style/themes
       themes: { light: "one-light", dark: "dark-plus" },
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -21,6 +21,7 @@
     "dayjs": "^1.11.19",
     "lodash.kebabcase": "^4.1.1",
     "remark-collapse": "^0.1.2",
+    "remark-github-blockquote-alert": "^2.0.1",
     "remark-toc": "^9.0.0",
     "satori": "^0.18.3",
     "sharp": "^0.34.5",
diff --git a/src/data/blog/2022/install-pihole-ha.md b/src/data/blog/2022/install-pihole-ha.md
@@ -138,9 +138,8 @@ vrrp_instance pihole {
 | 18   | The other nodes IPs                                                                                                                                                                                                                                                                      |
 | 23   | Node authentication. Keep in mind this is unencrypted, which is why we specify the other nodes by IP                                                                                                                                                                                     |
 | 32   | The script to run to verify DNS is live                                                                                                                                                                                                                                                  |
-
+> [!WARNING]
 > Never set an IP reservation for the virtual IP, or set it as a static address for another device
-> {: .prompt-warning }
 
 Also keep in mind, this is set up for unicast, but can be configured for multicast. I just like to be explicit. You can find more details about [keepalived configuration here](https://keepalived.readthedocs.io/en/latest/configuration_synopsis.html).
 
diff --git a/src/data/blog/2022/lxc-plex-setup.md b/src/data/blog/2022/lxc-plex-setup.md
@@ -26,8 +26,8 @@ Final provisioned LXC environment is as follows:
 
 Mounting my media share from a storage device was easy enough, once I realized I had to make the container privileged. I configured `fstab` to automount the share when the environment started, and used a credential file stored in /root for security.
 
+> [!TIP]
 > Privileged Container must be set to true to mount a network share
-> {: .prompt-tip }
 
 Lets start with the credential file. It's a simple file that needs to live somewhere fstab can access. I used /root because `fstab` will run as root so I know it will have access.
 
diff --git a/src/data/blog/2023/adding-figurine-to-login.md b/src/data/blog/2023/adding-figurine-to-login.md
@@ -12,8 +12,8 @@ I saw a very interesting video by [Alex Kretzschmar](https://www.youtube.com/wat
 
 To do this quickly and use the hostname for the login message, you can use thise script, otherwise follow along below
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 curl https://gist.githubusercontent.com/binarypatrick/2e33d8d3c79210dc74077627cb0deb9c/raw/ | sudo bash
diff --git a/src/data/blog/2023/back-up-rpi-live.md b/src/data/blog/2023/back-up-rpi-live.md
@@ -26,8 +26,8 @@ To install it, follow the guide on the github page, but here is a simplified ver
 
 ## Scripts Install
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 git clone https://github.com/seamusdemora/RonR-RPi-image-utils.git ./image-utils
@@ -53,8 +53,8 @@ sudo image-backup --initial /mnt/backup/$(date +"%Y-%m-%d").img,,5000
 
 The backup run time will depend on your device and how much data it needs to copy. It is surprisingly fast though. 15GB usually runs for 2+ minutes on a Raspberry Pi 4B.
 
+> [!WARNING]
 > Backup can be pretty large, ~15GB depending on how much you have running on your Pi
-> {: .prompt-warning }
 
 Once you have a completed backup, you can run an incremental backup by running `image-backup` and providing an existing backup to update.
 
diff --git a/src/data/blog/2023/bitwarden-automated-backup.md b/src/data/blog/2023/bitwarden-automated-backup.md
@@ -79,8 +79,8 @@ export BW_NOTIFICATION_EMAIL="<your_notification_email_address>"
 
 The scripts we're going to run live a repo named [BitwardenBackup](https://github.com/BinaryPatrick/BitwardenBackup). Definitely review the code that will be running. The script needs to be put somewhere the Bitwarden user can read it, and it needs to be set as executable.
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 REPO_BACKUP_SCRIPT=https://raw.githubusercontent.com/BinaryPatrick/BitwardenBackup/main/backup.sh
diff --git a/src/data/blog/2023/configuring-postfix-with-gmail.md b/src/data/blog/2023/configuring-postfix-with-gmail.md
@@ -39,8 +39,8 @@ smtp_use_tls = yes
 
 Notice that instead of adding your gmail credentials directly, we're adding them to a file named `gmail_credentials`. Your credentials will depend on whether you use multi-factor authentication (MFA/2FA) or not. If you are now, then you can just put your credentials directly into this file, otherwise you'll need to create an app password. It is highly recommended to use multi-factor authentication whenever possible so I'll assume you are.
 
+> [!TIP]
 > It is highly recommended to use multi-factor authentication whenever possible
-> {: .prompt-tip }
 
 Go to your [Google account page](https://myaccount.google.com/) and select _Security_ from the side navigation. Then in the center, select _2-Step Verification_. After verifying it's really you, scroll to the bottom and find _App Passwords_. From this page you can generate a new app specific password. I often select custom from the drop down and give it a descriptive name, then select _Generate_.
 
diff --git a/src/data/blog/2023/linux-on-dell-wyse-3040.md b/src/data/blog/2023/linux-on-dell-wyse-3040.md
@@ -24,8 +24,8 @@ This is pretty easy to do. In the BIOS, navigate to _Maintenance > Data Wipe_ an
 
 Picking a disto is tricky here. My device only had a 16 GB eMMC drive, which is really 14.8 GB. Most distros require 16 actually GB. Debian does not though and installing a minimal version works well for this low power device. Luckily Debian 12 (Bookworm) just came out so I used that. I also used [Ventoy](https://www.ventoy.net/en/download.html), but you however you choose get it on a USB stick and in the device.
 
+> [!TIP]
 > Debian 12 is a good pick with only 16 GB eMMC and 2 GB RAM
-> {: .prompt-tip }
 
 ![Debian 12 Install (Non-GUI)](../../../assets/images/2023/linux-on-dell-wyse-3040/debian-12-install.png)
 
@@ -37,8 +37,8 @@ I leave the root password empty. This will assign the initial user account to th
 
 Once Debian is installed, it may not boot up correctly. You may get an error saying `No bootable devices found`. Wyse devices require a `BOOTX64.EFI` file. To add this file, I loaded Debian Live and mounted the eMMC device. On my instance, the eMMC device has the label `mmcblk0p1`. Use the following to mount this device.
 
+> [!WARNING]
 > Wyse devices require a `/boot/efi/EFI/BOOT/BOOTX64.EFI` file to boot to the eMMC
-> {: .prompt-warning }
 
 ```bash
 sudo mkdir /mnt/debian
diff --git a/src/data/blog/2023/lxc-docker-setup.md b/src/data/blog/2023/lxc-docker-setup.md
@@ -73,8 +73,8 @@ docker compose version
 sudo usermod -aG docker $USER
 ```
 
+> [!WARNING]
 > You'll need to logout and log back in for the change to take effect
-> {: .prompt-warning }
 
 ## Installing Lazydocker
 
diff --git a/src/data/blog/2023/setup-rpi-uctronics-display.md b/src/data/blog/2023/setup-rpi-uctronics-display.md
@@ -54,8 +54,8 @@ Now that you've compiled and tested the file, it will need to be copied to the u
 sudo mv ./display /usr/bin/uctronics-display
 ```
 
+> [!WARNING]
 > Note that the binary is renamed to `uctronics-display` with the command
-> {: .prompt-warning }
 
 ## Autostart
 
diff --git a/src/data/blog/2023/show-ip-in-tty-login-prompt.md b/src/data/blog/2023/show-ip-in-tty-login-prompt.md
@@ -38,5 +38,5 @@ Debian GNU/Linux 11 \n \l
 eth0: \4{eth0}
 ```
 
+> [!WARNING]
 > Using DHCP it take a second for the system to establish an IP and you may see a blank value for the first few seconds after startup
-> {: .prompt-warning }
diff --git a/src/data/blog/2023/using-prune-to-manage-archives.md b/src/data/blog/2023/using-prune-to-manage-archives.md
@@ -14,8 +14,8 @@ Often times when using a tool like rsync to make backups you end up with lots of
 
 To install Prune you can go to the [releases page](https://github.com/BinaryPatrick/Prune/releases) and download the latest release for your environment. You can also just clone the repo and compile it yourself with the steps in the readme. If you are running Linux on x64 you can also run the following commands to download and install Prune.
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 curl https://raw.githubusercontent.com/BinaryPatrick/Prune/main/scripts/install-linux-x64.sh | sudo bash
diff --git a/src/data/blog/2025/restart-unhealthy-container.md b/src/data/blog/2025/restart-unhealthy-container.md
@@ -78,8 +78,8 @@ systemctl --user start restart-unhealthy.timer
 
 To make this easy, I created a gist that can be run from a script.
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 curl -s https://gist.githubusercontent.com/binarypatrick/d4faffc2807c1e68ddf1229acb057582/raw | bash
diff --git a/src/data/blog/2025/systemd-remounting-service-.md b/src/data/blog/2025/systemd-remounting-service-.md
@@ -102,8 +102,8 @@ systemctl status remount-share.timer && systemctl status remount-share.service
 
 All of this has been scripted to make it more convenient.
 
+> [!WARNING]
 > Don't just take my word for it. Always inspect the code that will be running on your machines, especially from an untrusted and unsigned source.
-> {: .prompt-warning }
 
 ```bash
 curl https://gist.githubusercontent.com/binarypatrick/d96331537d2976c3a05ce335b00697ca/raw | sudo bash -s -- "some_share_name"
diff --git a/src/layouts/PostDetails.astro b/src/layouts/PostDetails.astro
@@ -13,6 +13,7 @@ import { getPath } from "@/utils/getPath";
 import { slugifyStr } from "@/utils/slugify";
 import IconChevronLeft from "@/assets/icons/IconChevronLeft.svg";
 import IconChevronRight from "@/assets/icons/IconChevronRight.svg";
+import "remark-github-blockquote-alert/alert.css";
 import { SITE } from "@/config";
 
 type Props = {
