joost/website-zola
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

new journal post

Browse Source
This commit is contained in:
Joost Agterhoek 2024-09-08 21:36:20 +02:00
parent b2b027ec83
commit 5acb23e3b8
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/journal.md
View File

@ -4,6 +4,10 @@ date = 2024-09-06
draft = false draft = false
+++ +++
2024-09-08 😕
I need to get back into my `flask-soc-site`-project (project pages soon to come), but it is difficult: I have three different 'problems' I want to solve and it's hard to focus on just one. The difficulty is that my data and intended objects share a lot of similarities, but are not entirely the same: an IP address, a domain name, a URL, an email address. Would it make sense to make some higher 'host' class? And then have lower classes inherit certain traits from that class? Or does it make sense to even have a class at all?
## 2024-09-06 🚧 ## 2024-09-06 🚧
Not to say that it has been *easy* by any means, but, I think I have a setup now for this website: work on it locally in a Git repo (and Obsidian vault), test it from that folder, then push the code and rsync it to my server, where it should be automatically synced based on every change, including deletes. With that, I will delete most if not all of the boilerplate text here and maybe, just maybe, try writing this journal with anything tech- or development related. Not to say that it has been *easy* by any means, but, I think I have a setup now for this website: work on it locally in a Git repo (and Obsidian vault), test it from that folder, then push the code and rsync it to my server, where it should be automatically synced based on every change, including deletes. With that, I will delete most if not all of the boilerplate text here and maybe, just maybe, try writing this journal with anything tech- or development related.