get rid of “built on” updates
This commit is contained in:
@@ -5,7 +5,7 @@ permalink: /gitea/
|
||||
tags:
|
||||
- tinkering
|
||||
---
|
||||
This site is running in 11ty and is built locally and then the live site (which gets built into a folder called \_site) is pushed to my Reclaim Hosting account, where it's served up as kfitz.info. As an intermediate step, I have been pushing the code and content that builds the site to a GitHub repository, and then the \_site folder to another GitHub repository, kfitz-site, mostly for preservation/backup purposes; if something happens to the server or to my local repo, there's another version-controlled pile of code out there from which things can be rebuilt. (Technically, I pull kfitz-site from GitHub to Reclaim. Similarly, presentations.kfitz.info, which runs in revealjs, is built locally, pushed to GitHub, and then pulled to Reclaim.)
|
||||
This site is running in 11ty and is built locally, after which the live site (which gets built into a folder called \_site) is pushed to my Reclaim Hosting account, where it's served up as kfitz.info. As an intermediate step, I have been pushing the code and content that builds the site to a GitHub repository, and then the \_site folder to another GitHub repository, kfitz-site, mostly for preservation/backup purposes; if something happens to the server or to my local repo, there's another version-controlled pile of code out there from which things can be rebuilt. (Technically, I pull kfitz-site from GitHub to Reclaim. Similarly, presentations.kfitz.info, which runs in revealjs, is built locally, pushed to GitHub, and then pulled to Reclaim.)
|
||||
|
||||
I've had in my head for a while, though, that GitHub is in and of itself a point of failure, partially because of its ownership structure. On top of which, I haven't been delighted knowing that everything I push there is part of the greater Copilot feeding frenzy.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user