scubbo/blogcontent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add app-sync job to publish workflow

Browse Source
This commit is contained in:
Jack Jackson 2025-02-26 19:43:58 -08:00
parent 589aa1e202
commit 31d883da41
2 changed files with 26 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
.gitea/workflows/publish.yaml
View File

@ -72,4 +72,28 @@ jobs:
gitea.scubbo.org/scubbo/blogcontent:latest gitea.scubbo.org/scubbo/blogcontent:latest
gitea.scubbo.org/scubbo/blogcontent:${{ gitea.sha }} gitea.scubbo.org/scubbo/blogcontent:${{ gitea.sha }}
# TODO - update deployment with new image update-deployment-repo:
runs-on: ubuntu-latest
needs:
- build-and-push
steps:
- name: Check out deployment repo
uses: actions/checkout@v4
with:
repository: gitea.scubbo.org/scubbo/blog-deployment
- name: Install kustomize
run: |
apt-get update && apt-get install -y kustomize
- name: Update deployment
run: |
kustomize edit set image image_name=*:${{ gitea.sha }}
- name: Commit and push
run: |
git config --global user.email "auto-updater@scubbo.org"
git config --global user.name "UpdaterBot"
git add .
git commit -m "Update blog content to ${{ gitea.sha}}"
git push

2
blog/content/posts/weeknotes-the-first.md
View File

@ -94,4 +94,4 @@ I've been meaning to migrate away from Drone as my CI/CD provider for a while no
[^untrustworthy]: I particularly appreciated the recognition that "_a lot of better informed people have sworn off LLMs entirely because they can’t see how anyone could benefit from a tool with so many flaws. The key skill in getting the most out of LLMs is learning to work with tech that is both inherently unreliable and incredibly powerful at the same time. This is a decidedly non-obvious skill to acquire!_" [^untrustworthy]: I particularly appreciated the recognition that "_a lot of better informed people have sworn off LLMs entirely because they can’t see how anyone could benefit from a tool with so many flaws. The key skill in getting the most out of LLMs is learning to work with tech that is both inherently unreliable and incredibly powerful at the same time. This is a decidedly non-obvious skill to acquire!_"
[^writing-to-think]: in fact that would entirely defeat the purpose of "_writing in order to figure out what you think_". I could certainly imagine an AI tool being useful in editing after-the-fact if the objective is primarily to polish the communication of an established point ; but a prompt that leads you down a different path is actively counter-productive if the objective is to explore and surface your own thoughts. [^writing-to-think]: in fact that would entirely defeat the purpose of "_writing in order to figure out what you think_". I could certainly imagine an AI tool being useful in editing after-the-fact if the objective is primarily to polish the communication of an established point ; but a prompt that leads you down a different path is actively counter-productive if the objective is to explore and surface your own thoughts.
[^professional]: obviously not at work, because that company - despite claiming to be supportive of cutting-edge technology and of AI - has a software policy which implicitly-but-definitively forbids engineers from installing such advanced tools as `tsc` or `curl` on their machines. Lawyers, man... [^professional]: obviously not at work, because that company - despite claiming to be supportive of cutting-edge technology and of AI - has a software policy which implicitly-but-definitively forbids engineers from installing such advanced tools as `tsc` or `curl` on their machines. Lawyers, man...
[^gitea-actioned]: if you can see this footnote, this diff was published via Gitea Actions! :) [^gitea-actioned]: if you can see this footnote, this diff was published via Gitea Actions! And if you can see _this_ sentence, the deployed architecture was automatically updated upon publication, too :)