freyjagp/blog.raer.me
1
0
Fork 0
Code Actions Packages Releases Activity

Add table of contents to old blogs

Browse Source
This commit is contained in:
Freyja Odinthrir
2024-09-27 13:56:48 -07:00
parent a93700b334
commit b357ab14b4
6 changed files with 70 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
content/2024/01/18/increasing-complexity.md
View File

@@ -2,6 +2,13 @@ title: Increasing complexity
description: A small issue snowballs because I want independence
tags: technical, gitops, devops
date: 2024-01-18 01:09
edited: 2024-09-27 13:52
# Table of Contents <!-- omit in toc -->
- [Increasing Complexity](#increasing-complexity)
- [Actually doing the thing](#actually-doing-the-thing)
- [Getting my fork on my package repo](#getting-my-fork-on-my-package-repo)
# Increasing Complexity
@@ -88,11 +95,11 @@ This isn't my first rodeo with setting these things up, though. I've got a simil
Okay. Enough talk, already! Lets do this!
## Actually doing the thing
# Actually doing the thing
So all that stuff I was talking about before was more-or-less me brainstorming what I needed to do. Here's some reporting back from me doing the stuff.
### Getting my fork on my package repo
## Getting my fork on my package repo
Turns out, the makefile is fine. Super easy. Just gotta hit it with a `make` command and its primo. So what I did, was I made the mirrors org and moved my blag mirror over there. Then I forked it to my personal gitea account. Then I cloned the fork, and made a `v2.3.0` branch because it was on `v2.2.x`. I updated the version in the source. Then I added the dependency for the new package `pymdown-extensions` in the appropriate files. Then I modified the `markdown.py` file to include the `footnotes` and `pymdownx.tilde` (strikethrough) extensions. Then I ran the makefile, which did its magic and made the stuff. Then I simply run twine to upload to my personal gitea package repo. Done. Version 2.3.0 is on my repo.