mirror of
https://github.com/Brandon-Rozek/website.git
synced 2025-10-08 22:21:12 +00:00
Fixed links
This commit is contained in:
parent
18ca6cae06
commit
1bb95f36d7
27 changed files with 100 additions and 100 deletions
|
@ -10,7 +10,7 @@ tags:
|
|||
title: Automatically Updating Podman Containers
|
||||
---
|
||||
|
||||
Recently, I have been [transitioning to Podman](/blog/rootless-docker-compose-podman) for running my container infrastructure. In the process, I brought over Watchtower which I have previously used for auto-updating docker containers. Before doing so, I didn't check its [compatibility](https://github.com/containrrr/watchtower/issues/1060) (whoops) and found a few of my containers would every other week or so not come back up.
|
||||
Recently, I have been [transitioning to Podman](/blog/rootless-docker-compose-podman/) for running my container infrastructure. In the process, I brought over Watchtower which I have previously used for auto-updating docker containers. Before doing so, I didn't check its [compatibility](https://github.com/containrrr/watchtower/issues/1060) (whoops) and found a few of my containers would every other week or so not come back up.
|
||||
|
||||
I then remembered that I restart my server for general system updates almost every day. What if I perform the podman container updates on start up? After modiyfing my systemd service to include an extra field called `ExecStartPre` and removing Watchtower, I found no more missing containers! The field `ExecStartPre` performs a pull (update) before starting up the containers via `ExecStart`.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ medium_enabled: true
|
|||
|
||||
There are many times that I need to slightly mess with a color. The easiest way I found to do it is to use one of the many color functions in the program `Sass`. [Sass](https://sass-lang.com/) is a CSS preprocessor, meaning that it has it's own syntax and it compiles down to CSS. I remember using this before CSS variables became a thing and that was one of the main driving points of Sass.
|
||||
|
||||
Since I don't work in Web Development anymore, I don't actually have Sass installed on my computer but instead go to [SassMeister.com](https://www.sassmeister.com/) to do my color manipulations. ThoughtBot already wrote a really nice [post](https://thoughtbot.com/blog/controlling-color-with-sass-color-functions) describing all the different color functions, but I'll quickly describe what I do to mess with colors.
|
||||
Since I don't work in Web Development anymore, I don't actually have Sass installed on my computer but instead go to [SassMeister.com](https://www.sassmeister.com/) to do my color manipulations. ThoughtBot already wrote a really nice [post](https://thoughtbot.com/blog/controlling-color-with-sass-color-functions/) describing all the different color functions, but I'll quickly describe what I do to mess with colors.
|
||||
|
||||
## Quick Color Manipulation
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ For the longest time I've held out on deploying my website through GitHub action
|
|||
|
||||
> If I have to execute `git push`, I might as well run a `./sync` script afterwards.
|
||||
|
||||
What convinced me otherwise is automated commits. I currently have GitHub actions that sync my [Mastodon toots](/toots) and [iNaturalist observations](/observations). As part of the sync process, a git commit is made. This commit should then trigger a site rebuild.
|
||||
What convinced me otherwise is automated commits. I currently have GitHub actions that sync my [Mastodon toots](/toots/) and [iNaturalist observations](/observations/). As part of the sync process, a git commit is made. This commit should then trigger a site rebuild.
|
||||
|
||||
How do we create a GitHub action that builds a Hugo website and deploys it via `rsync`? The rest of this post will go over the components of the GitHub action that triggers when I update my website.
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ tags: ["Amateur Radio"]
|
|||
medium_enabled: true
|
||||
---
|
||||
|
||||
In this post, I will describe a low cost way to get started with digital modes using FM. We will extend off my [previous post](/blog/digitalmodes). Even though some of these instructions are hardware specific, I hope that the general principles will apply to whatever hardware you're working with.
|
||||
In this post, I will describe a low cost way to get started with digital modes using FM. We will extend off my [previous post](/blog/digitalmodes/). Even though some of these instructions are hardware specific, I hope that the general principles will apply to whatever hardware you're working with.
|
||||
|
||||
In order to transmit, you will need an amateur radio license. We are going to be transmitting within 145.50-145.80 Mhz which according to the [ARRL Band Plan](http://www.arrl.org/band-plan) is marked as the miscellaneous and experimental section. In terms of our encoding scheme, let's play around with [8PSK](https://www.sigidwiki.com/wiki/8PSK).
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ tags: ["Git"]
|
|||
medium_enabled: true
|
||||
---
|
||||
|
||||
The Linux kernel community make use of patches in git to share code changes with one another. Patches are only nicely formatted differences between your current codebase and what you compare it to. If you want to share a subsetted git tree, then [git bundle](/blog/gitbundle) would be the way to go.
|
||||
The Linux kernel community make use of patches in git to share code changes with one another. Patches are only nicely formatted differences between your current codebase and what you compare it to. If you want to share a subsetted git tree, then [git bundle](/blog/gitbundle/) would be the way to go.
|
||||
|
||||
## Creating the patch
|
||||
|
||||
|
|
|
@ -552,4 +552,4 @@ Notice that a couple times in the proof, make use of a tactic called `linarith`.
|
|||
|
||||
That concludes the examples I gave for my talk. For each proof, you can see that I included at least two different ways of going about proving it. I generally prefer the inference style method where we explicitely call on `Or.elim` and the like. Though when it comes to double induction, I have not figured out how to apply `rec_on` multiple times in a clean way.
|
||||
|
||||
In the process of making this tutorial, I released other lean posts. One that I recommend checking out is ["Readable Lean 3 Proofs"](/blog/readable-lean3-proofs). In it, I give my opinions on how to make the written out proofs more human friendly.
|
||||
In the process of making this tutorial, I released other lean posts. One that I recommend checking out is ["Readable Lean 3 Proofs"](/blog/readable-lean3-proofs/). In it, I give my opinions on how to make the written out proofs more human friendly.
|
||||
|
|
|
@ -7,7 +7,7 @@ tags: []
|
|||
title: Netboot.xyz Bootloader
|
||||
---
|
||||
|
||||
Instead of manually loading ISOs onto a USB stick for [Ventoy](/blog/ventoy) to display, we can use Netboot.xyz to present us a list of options and download them during boot. This requires an internet connection in order to work.
|
||||
Instead of manually loading ISOs onto a USB stick for [Ventoy](/blog/ventoy/) to display, we can use Netboot.xyz to present us a list of options and download them during boot. This requires an internet connection in order to work.
|
||||
|
||||
Netboot.xyz is commonly used for PXE booting, but in this post I'll describe using it as an ISO.
|
||||
|
||||
|
|
|
@ -5,7 +5,7 @@ draft: false
|
|||
tags: [ "Python" ]
|
||||
medium_enabled: true
|
||||
---
|
||||
**Deprecated in favor of [pip install editable](/blog/pipeditable)**
|
||||
**Deprecated in favor of [pip install editable](/blog/pipeditable/)**
|
||||
|
||||
I've found it to be incredibly helpful to emulate having a library installed on my system rather than depending on my local directory path to pick up my file edits. To do this in a python project where you've defined a `setup.py`, you can specify the command `develop`.
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ tags: [ "Linux" ]
|
|||
medium_enabled: true
|
||||
---
|
||||
|
||||
**Note:** [Currently I favor using `bmaptool`](/blog/bmaptool-iso)
|
||||
**Note:** [Currently I favor using `bmaptool`](/blog/bmaptool-iso/)
|
||||
|
||||
This blog post is going to assume that we're writing to `/dev/sdX`. Please change this to whatever disk you're actually trying to write to. I bear no responsibility if you accidentally write to your OS drives.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ medium_enabled: true
|
|||
|
||||
Git and their various hosting platforms support commit signing as an additional step of verification. There seems to be an active debate on whether it should be used regularly, though I'll describe it on here in case you want to set it up.
|
||||
|
||||
You'll need to have a [GPG key already created](/blog/gpgkeygen).
|
||||
You'll need to have a [GPG key already created](/blog/gpgkeygen/).
|
||||
|
||||
First locate the key you want to sign with
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ The [IndieWeb movement](https://indieweb.org) is focused on people controlling t
|
|||
|
||||
The recommended syndicate or copy content is through a technique called [Publish Own Site Syndicate Elsewhere (POSSE)](https://indieweb.org/POSSE). First the author posts on their own website, and then a function takes that post and publishes it on another website.
|
||||
|
||||
However, this is not what I am currently doing to [show my Mastodon toots](/toots). Instead I have implemented [Publish Elsewhere Syndicate Own Site (PESOS)](https://indieweb.org/PESOS). In this model, I first publish directly on Mastodon and then have a function query the Mastodon server to update my personal website.
|
||||
However, this is not what I am currently doing to [show my Mastodon toots](/toots/). Instead I have implemented [Publish Elsewhere Syndicate Own Site (PESOS)](https://indieweb.org/PESOS). In this model, I first publish directly on Mastodon and then have a function query the Mastodon server to update my personal website.
|
||||
|
||||
## Advantages to PESOS
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue