Revisiting Ironsworn
We go back into the land of the Ironsworn campaign and do a little software development in the process.
Way back in February I did a solo session in the original Ironsworn game, and i've been meaning to get back to it.
Alex Ward
But, I've also been writing a lot about getting solo TTRPG sites up and have been having a lot of fun playing with the Iron Vault plugin in Obsidian.
Alex Ward
So, this week I've spent a fair amount of time converting over the Ironsworn campaign from that first post, cleaning up the markdown-it plugin, and generally doing some more work getting the site up.
Ironsworn Session 2 - To the Cairnlands!
If you remember the last session (or go reread it), Ael made a vow to an Aesir spirit to go find a particular Axe which is in the Cairnlands and then give it to his son, Vul.
He doesn't know where the axe is, other than "that-a-way", so he's going to go on a journey of discovery and self reflection now that he's no longer cursed.
The transcript (with rendered Obsidian blocks) is here:
Making more progress with Markdown-it
Last time, I had just made a markdown-it plugin and stored it in with the starter repository. Now I've made it its own package, located here:
The intention is to eventually publish it to npm if anyone else besides me finds it useful. This time it now supports more of the blocks, and allows you to pass your own templates in as part of the 11ty rendering process.
Hooray!
Deploying to Fly.io this time
If you're interested in doing a deployment to a more developer-centric platform, fly.io is a neat little service that takes Docker containers and distributes them along the number of edge nodes you specify.
They used to have a free tier, but since static sites require barely any resources you can run them for basically nothing. The only issue is going to be if you get a ton of traffic and you have a dedicated IP. Fly's pricing page on bandwidth is a little confusing, but they have this in there:
Data transfer from apps without an assigned IP address is free.
So, I think so long as you don't have a dedicated IP (which should be unnecessary for a static site) you shouldn't get bandwidth charges. Likewise, the amount of data you're transmitting for a static site should also be very small.
The other cool thing is that the machines can go idle and start up quickly, so you're only charged when you're actively receiving traffic. If that's not very often, you're barely being charged at all.
I'll let y'all know what my first month's bill winds up being.
Running a static website is quite simple, if you know a little bit about docker. They have some "old" instructions on how to do this, but they still work just fine:
And here it is running Live
And away we go!