mat
/
mat.services
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use p for figcaptions

pull/1/head
mat ess 2022-10-16 21:25:58 -04:00
parent 089dedb94c
commit e9ec3881ae
3 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/posts/gitea-on-fly-io/index.md
View File

@ -170,14 +170,14 @@ Uh. Hm. I just got an email saying a Fly.io instance ran out of memory and crash
<figure>
<img alt="Fly.io memory dashboard" src=fly-io-memory-dashboard.webp />
<figcaption><h4>Fly.io memory dashboard</h4></figcaption>
<figcaption><p>Fly.io memory dashboard</p></figcaption>
</figure>
That doesn't look so great. It seems like Gitea idles just under the amount of memory we have with a default instance size, and operations like `git push` can bump it over the threshold to an out-of-memory error. Let's check out the "Scale" section of the dashboard, and increase the memory allotment for this VM:
<figure>
<img alt="Fly.io VM scaling interface" src=fly-io-scale-vm.webp />
<figcaption><h4>Fly.io VM scaling interface</h4></figcaption>
<figcaption><p>Fly.io VM scaling interface</p></figcaption>
</figure>
You can also use `flyctl` to scale your app!

5
sass/style/parts/_image.scss
View File

@ -27,14 +27,15 @@ figure img {
}
}
figure h4 {
figure p {
font-size: 1rem;
margin: 0;
margin-bottom: 1em;
}
figure h4::before {
figure p::before {
content: "↳ ";
font-weight: bold;
}
svg {

2
templates/macros/macros.html
View File

@ -80,7 +80,7 @@
<img width=1024 height=512 class="hero" alt="{{ page.extra.heroPrompt }} - generated using Stable Diffusion"
src=hero.webp />
<figcaption>
<h4><i>{{ page.extra.heroPrompt }}</i> - generated using Stable Diffusion</h4>
<p><i>{{ page.extra.heroPrompt }}</i> - generated using Stable Diffusion</p>
</figcaption>
</figure>
{% endif %}