Add new post. Multiple other uncommited changes.

This commit is contained in:
James Pace 2024-01-13 17:25:46 +00:00
parent aa7043fd1c
commit 3c2d8da31d
7 changed files with 56 additions and 20 deletions

View File

@ -2,13 +2,12 @@ project:
type: website
website:
title: "howl121"
title: "TIL"
search: false
navbar:
left:
- href: index.qmd
text: Home
- about.qmd
- posts.qmd
format:

View File

@ -1,14 +0,0 @@
---
title: "About"
toc: false
---
Howl121 focuses on providing How Tos and Reviews that are technical in nature and of interest
to individuals working with Open Source or low cost robotics.
## Want to work with us?
We're very open on suggestions on thing to review or how tos that people are interested in.
Feel free to contact James at james@how121.com with suggestions or any other inquiries.

View File

@ -0,0 +1,27 @@
---
title: "Bash has a builtin network client"
author: "James Pace"
date: "2024/01/12"
---
I've been playing with using Rust on microcontrollers that have
ethernet support with the microcontroller using UDP to communicate
with the rest of the world.
When testing the code I wrote on the microcontroller, I searched for how to send
udp packets from the command line (expecting to find the right incantation for
netcat, which I've used in the past but don't remember the options for.)
What I actually found was more interesting.
Apparently, bash has builtin "pseudo devices" that allow you to read and write
from a TCP or UDP port like you were reading or writing from a file.
For example, to send the string "hello" to my microcontroller at 192.168.1.109 on
port 1337, I used the command
```bash
echo "hello" > /dev/udp/192.168.1.109/1337
```
Bash supports the same thing for TCP connections as well using similar syntax.
That is a lot easier to remember than netcat, and I'll definitely use
it again.

View File

@ -1,5 +1,5 @@
---
title: "Quick Review of Just"
title: "Just: A quick review"
author: "James Pace"
date: "2024/01/10"
---
@ -24,6 +24,7 @@ test:
the command `just test` will call `cargo test --features log` in the current terminal window.
Compared to `make`, `just`:
1. Eliminates the need for manual .PHONY target creation, saving you time and reducing
clutter in Justfiles compared to Makefiles.
2. Can be called below the directory the `Justfile` is in and still find the `Justfile`

View File

@ -0,0 +1,19 @@
---
title: "Summary of Free Self Hosted Git Options"
author: "James Pace"
date: "2024/01/12"
draft: true
---
<!--
Why:
1. All sorts of programming tools support git and using git for versioning.
2. Expecially with gitops being a real thing.
3. But we want to maintain control and be able to still operate completely offline.
Options:
1. Gitea
2. gitlab
3. onedev
4. gerrit
-->

View File

@ -5,10 +5,13 @@ listing:
id: blog-listing
contents: blog
type: table
fields: [date, title]
fields: [title, date]
sort: "date desc"
---
Howl121 provides data focused reviews related to low cost robotics and drones.
TIL focuses on things I learned "today" with an emphasis on robotics and
open source software.
## Latest Posts

View File

@ -4,5 +4,6 @@ toc: false
listing:
contents: blog
type: table
fields: [date, title]
fields: [title, date]
sort: "date desc"
---