No description
.forgejo/workflows | ||
images | ||
embed_fonts.py | ||
LICENSE | ||
README.md | ||
signature_base64_generated.html | ||
signature_hotlinked_generated.html | ||
signature_template.html |
Aichan Mail Signature
My email signature in two variants: hot-linked images and embedded (base64) images
Image URLs
Links for images are served from Forgejo raw URLs:
https://git.prisma.moe/aichan/aichan_mail_signature/raw/branch/main/images/{filename}
Automatic Base64 Generation
The Forgejo Actions workflow (.forgejo/workflows/generate-signature.yml
) automatically:
-
Triggers on:
- Push to
main
/master
branch - Changes to
images/
orsignature_template.html
- Manual trigger via Forgejo UI
- Push to
-
Process:
- Reads
signature_template.html
- Converts all images in
images/
to base64 - Minifies output (removes whitespace between tags)
- Generates
signature_base64_generated.html
- Auto-commits and pushes (with
[skip ci]
to prevent loops)
- Reads
Usage
Option A: Hot-Linked Signature
-
Push to Forgejo:
git add . git commit -m "Update signature" git push
-
Copy to Mail:
- Open
signature.html
in browser - Select all (Ctrl+A), Copy (Ctrl+C)
- Paste into the mail signature editor
- Open
Pros: Lightweight, easy to update Cons: Requires external image loading
Base64 Signature (Maximum Compatibility)
-
Wait for CI/CD to generate
signature_base64_generated.html
-
Copy to Mail:
- Open
signature_base64_generated.html
in browser - Select all, copy, paste
- Open
Pros: Works offline, no external dependencies Cons: Larger file size (144K)
Updating Images
Just replace files in images/
folder and push:
cp ~/new_logo.png images/aichan.moe.png
git add images/aichan.moe.png
git commit -m "Update aichan.moe logo"
git push
Hot-linked signature: Updates immediately Base64 signature: Auto-regenerated by CI/CD in ~1 minute