summaryrefslogtreecommitdiff
path: root/content/entry/journal-update-022.md
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2022-12-04 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2022-12-04 00:00:00 +0000
commitd0def1af0a9f369d3c179f80c0cae34811036bb4f972b95627c96c70021e43c5 (patch)
tree05dfd6a4068a323ccbf4027e80fedc5befc69cead2ef43ae13178df9cc2b6bc3 /content/entry/journal-update-022.md
parent9a8a9cc9de5773104ff0f599727ce0976c6499b626f7830ba895bdf2e655ad54 (diff)
downloadjournal-d0def1af0a9f369d3c179f80c0cae34811036bb4f972b95627c96c70021e43c5.tar.gz
journal-d0def1af0a9f369d3c179f80c0cae34811036bb4f972b95627c96c70021e43c5.zip
New entry: journal-update-022
Diffstat (limited to 'content/entry/journal-update-022.md')
-rw-r--r--content/entry/journal-update-022.md30
1 files changed, 30 insertions, 0 deletions
diff --git a/content/entry/journal-update-022.md b/content/entry/journal-update-022.md
new file mode 100644
index 0000000..5e04e27
--- /dev/null
+++ b/content/entry/journal-update-022.md
@@ -0,0 +1,30 @@
+---
+title: "Journal Update 022"
+date: 2022-12-04T00:00:01
+draft: false
+pageinfo: true
+---
+## What's New
+In my last journal entry update back in September[1], I talked about rebranding away from nicksphere to just my name, nicholasjohnson. Well I've finished the rebranding. For more on that, see my previous journal entry.[2] I accomplished it by the most straightforward way possible: setting up everything in parallel on a fresh server, then updating the domains. I changed some backend server stuff, but probably nobody cares about those details.
+
+Using Ansible, I automated configurations that remain the same across servers I use. At some point in the future when it's ready, I'll git push the playbook. I decided not to automate the entire server. For every change I make on the server, I'd have to update the Ansible scripts, creating twice the work. It would only save me time in the scenario where my server is wiped and I need to reprovision it from scratch. That situation is very rare, so automating isn't worth it.
+
+My new VPS accepts many payment methods, so I don't depend on digital tulips[3] anymore. Unfortunately my VPS provider doesn't have IPv6 support yet, but I've been assured that they already have the IPv6 addresses and they're just working on assigning them now.
+
+I decided to drop I2P support for the time being. It was broken anyways for who knows how long. If you want to know more about that, read this Git commit message[4]. If you use the Tor onion[5][6] to access this journal, nothing has changed. I migrated the onion to the new VPS as-is.
+
+## Future Plans
+For the Hugo theme for this journal, you can find my plans in this TODO file[7]. I'm going to start versioning the theme. Once I implement the features in the TODO file, as long as nothing else occurs to me, I'll make the first official release of the theme with version 1.0.0.
+
+As for the journal itself, eliminating the promoted links page[8] is the only major change I have planned and that will happen gradually.
+
+
+Link(s):
+[1: Journal Update 021](/2022/09/19/journal-update-021/)
+[2: Domain Change Announcement](/2022/12/04/domain-change-announcement/)
+[3: Glossary: Digital Tulips](/glossary/)
+[4: Drop I2P Support](https://git.nicholasjohnson.ch/journal/commit/?id=85b77079ffea8fae7f29516dc029812000c457fb)
+[5: Tor Onion Capsule](gemini://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion)
+[6: Tor Onion Site](http://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion)
+[7: hugo-theme-journal TODO](https://git.nicholasjohnson.ch/hugo-theme-journal/tree/TODO?id=33f2df0c33830298bef1e35fc6dc49fe1df23c8e)
+[8: Promoted Links](/promoted/)