Well, wraping up WELL after the project end date of May 28th. Personal and family events take precidence over personal project. However, I’m still satisfied with what I have been abel to accomplish - mainly the recipe sub-site that can help archive family recipe history, and sketches for where to go from here.
As an adjacent item, I’ve begun to use Obsidian. While Obsidian itself is not open source, it saves all the core data on local disk as Markdown, and with it’s extensive plugin system and sync between multiple devices, it solves a pain-point or providing access to my main task system on the phone.
Recipe archiving is continuing slowely. Now that the holiday is over, and before my next big adventure for are yearly work gathering, I’d like to continue a more holistic view of my data archive. Items I’d like to archive
My “journal” in markdown format - daily thoughts, etc. My “bullet journal” in markdown format - daily tasks, zettlekrasten, etc. recipe - personal recipe. photos - JPEG formatted photos. As part of this I"ve sketched out a new repo - private for now - that will contain code to replicate the markdown repos, as well as organize, format, and archive the photos.
So good progress has been made storing my recipes. Right now I have a collection of public resources (recipes, this blog) and private repositories (A bullet journal for daily tasks, a journal for adhoc writing). But all of these only only encompass text, and in the case of the blog, smaller images I feel comfortable storing in git. What do I do with larger image collections?
After some review of git-annex and git-lfs, I realize that I’d rather avoid placing the files in a system that would require external software to review.
With the template complete, I spent last night and tomorrow deploying the family recipe site recipe.r15cookie.com. Deployed as a Github Pages project, it seems to work fairly well. At one point I wanted to automated the deployment more, but given the work to coordinate between Github pages setup, the custom domain, and Cloudflare, in the end it was easy to do manually then to figure out how to coordinate between the three.
The main hugo template site is finished! Unfortunately had a LOT of personal sickness/other priorities the drove me away from the project. But in the sprit of finishing this, I want to at least post my recipe site!
My thoughts also turn to building out a workflow that would let me work on content or infrastructure from my mobile device. In that way, it would be easy to use small amounts of idle time.
Sickness has run it’s course through the family, and unfortunately has prevented me from devoting the time I wanted to. I was able to scoop a little bit of time this morning, and have a functioanl terraform template working. The PR is not merged yet, as I need to get a working Github Action pipeline functional first. Hopefully in the next few days.
My overall goal was to make the r15-papercss-hugo-theme easily hostable.
While a bit of a distraction, I wanted to ensure my primary template had a good demonstration. CloudFlare’s Pages seems perfect. A generic static website hosting, and has built in support for Hugo. But despite the confiugration made available in the GUI, I was unable to get the Cloudflare working to accept the custom parameters I needed to allow the exampleSite within the template to work.
My new plan is to leverage a traditional Github Action workflow to build out the site, then manually upload the assets to Cloudflare.
A busy day, so just stuck with updating the template on my main blog to match the template update I made on 2/19. Also some minor cleanup, as I no loger have the GitPod links on my readme page.
Although raw ASCII text is my plan for data preservation, most people would like to view/browse information. Hugo is the static site generator I use for my public site. I’ve had a desire to keep family recipe, and coffee reviews, publically available. With that smaller goal in mind, I updated my hugo template to include recipe and coffee subtypes, as a first step.
I should say mine with an astrisk that my template is a copy of the original PaperCSS Hugo Template but was archived last year.
First day of my 100 day project to perserve information! Most of today was spent building out this project page! In effect this post itself is a representation of what I wish to accomplish - storing data in a format that is accessible for future. In that regard, the raw data is in ASCII format - probably the most readable text format, at a base level.
My primary “base” formats will be ASCII for text, and JPEG for images.
Kicking off a 100 Day Project focused on buiding a system for perserving data long-term. Daily blog will ber located in the Perserving Info Project Space. Overall kind of excited - and gives me a nice personal project to grind away at. Good to get back into writing. And this blog serves as a good basis for the project - a complete text representation existing within My Primary and Secondary archive locations, in pure text.