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

Migrate to blag

Browse Source 
- Convert old html blogposts to markdown
- Organize things into blag's folder structure
- Adjust html and css templates
This commit is contained in:
Freyja Odinthrir
2024-01-17 12:04:35 -08:00
parent ed482a34e9
commit 7922bab8e3
29 changed files with 704 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
content/2023/07/03/doing-more-stuff.md Normal file
View File

@@ -0,0 +1,47 @@
title: Doing more stuff...
description: doing more stuff with the blog
tags: ruminations
date: 2023-07-03 16:20
# Doing more
Now that I have gitea (and a mysql server) in 'prod', its time to do more automagical things. The first line of business will be to look into CI/CD tools with gitea. Its rather silly that I have a whole-ass gitea server running, but don't utilize any of the ci/cd features that it offers. At a minimum, I could set up something to update this webserver automatically based off of a git repo push, instead of the current method: sftp directly into the freebsd host, navigate to the jail's html folder, and editing things directly. I'm literally editing this thing LIVE in vscode right now, lol. The moment I hit save, is the moment it gets published. I could maybe stand to do things a *little* different...? Possibly? Or maybe I won't. Maybe I'll just say "Fuck it, that's too much work, this site is full on low-effort". IDK. It depends on how much I think going 'low effort' will end up causing me to have an annoying, repetative workflow when editing this site.
---
__EDIT: 2024-01-17 11:27__
This was imported from the old version of this blog. Here is the original html version:
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>TEMPLATE</title>
</head>
<body>
<nav>
<a href="/index.html">Index</a>
<a href="/about.html">About</a>
<a href="/contact.html">Contact</a>
</nav>
<hr>
<!-- CONTENT GOES HERE -->
<h1>Doing more.</h1>
<p>Now that I have gitea (and a mysql server) in 'prod', its time to do more automagical things. The first line of business will be to look into CI/CD tools with gitea. Its rather silly that I have a whole-ass gitea server running, but don't utilize any of the ci/cd features that it offers. At a minimum, I could set up something to update this webserver automatically based off of a git repo push, instead of the current method: sftp directly into the freebsd host, navigate to the jail's html folder, and editing things directly. I'm literally editing this thing LIVE in vscode right now, lol. The moment I hit save, is the moment it gets published. I could maybe stand to do things a *little* different...? Possibly? Or maybe I won't. Maybe I'll just say "Fuck it, that's too much work, this site is full on low-effort". IDK. It depends on how much I think going 'low effort' will end up causing me to have an annoying, repetative workflow when editing this site.</p>
<!-- END CONTENT -->
<hr>
<footer>
<p>Published: 3rd July, 2023 @ 4:20pm PDT</p>
</footer>
</body>
</html>
```

76
content/2023/07/03/ha.md Normal file
View File

@@ -0,0 +1,76 @@
title: Ha!
description: a discovery of sorts
tags: ruminations
date: 2023-07-03 15:36
# Ha!
I've tracked down an issue that plagued my gitea config and made me go nuts for a week. Turns out that for some reason, full end-to-end https on gitea breaks ssh pushing? I've abandoned this prospect for now, instead opting to just use TLS termination at <https://gitea.raer.me/> and forwarding to http on the private network. That's fine for my purposes. Its not ideal. But its fine.
What truly matters here, is that I've got my gitea deployment off of the virtual machine it was running on. And, the database connection is now encrypted (and enforced) with tls. So there's that. See, before, I was running a virtual machine on my truenas scale server that had a bunch of rootless docker instances running things. this was far. Too. Complex. It didn't even solve anything practically, either. It forced me to do networking where I didn't need to.
Instead, gitea and its mysql server run directly on the k3s implementation on my truenas scale server. This is ideal, as it allows me easier control over the files. It allows me to do zfs snapshots of the db and the gitea server. It removes the need for the scheduled daily downtime while a script archived and stored the whole thing on another server. At least, that's the idea. It also removes the overhead of the whole server, and streamlines things somewhat.
Anyway, this has been an entry in the ol blog. Over and out
- Freyja
ps: did I mention I didn't have to nuke the whole thing and start from scratch like I thought I might? That's a big bonus!
---
__EDIT 2024-01-17 11:29__
This was copied from its original HTML version. See below:
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Ha!</title>
</head>
<body>
<nav>
<a href="/index.html">Index</a>
<a href="/about.html">About</a>
<a href="/contact.html">Contact</a>
</nav>
<hr>
<!-- CONTENT GOES HERE -->
<h1>Ha!</h1>
<p>I've tracked down an issue that plagued my gitea config and made me go nuts for a week. Turns out that for some
reason, full end-to-end https on gitea breaks ssh pushing? I've abandoned this prospect for now, instead opting to
just use TLS termination at https://gitea.raer.me/ and forwarding to http on the private network. That's fine for my
purposes. Its not ideal. But its fine.</p>
<p>What truly matters here, is that I've got my gitea deployment off of the virtual machine it was running on. And, the
database connection is now encrypted (and enforced) with tls. So there's that. See, before, I was running a virtual
machine on my truenas scale server that had a bunch of rootless docker instances running things. this was far. Too.
Complex. It didn't even solve anything practically, either. It forced me to do networking where I didn't need to.
</p>
<p>Instead, gitea and its mysql server run directly on the k3s implementation on my truenas scale server. This is ideal,
as it allows me easier control over the files. It allows me to do zfs snapshots of the db and the gitea server. It
removes the need for the scheduled daily downtime while a script archived and stored the whole thing on another
server. At least, that's the idea. It also removes the overhead of the whole server, and streamlines things
somewhat.</p>
<p>Anyway, this has been an entry in the ol blog. Over and out.</p>
<p>ps: did I mention I didn't have to nuke the whole thing and start from scratch like I thought I might? That's a big
bonus!</p>
<p>- Freyja</p>
<!-- END CONTENT -->
<hr>
<footer>
<p>Published: 3rd July, 2023 @ 3:36pm PDT</p>
</footer>
</body>
</html>
```