Use yaml frontmatter
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
parent
d9964492f3
commit
3d71e6ab08
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "about me"
|
||||
path = "about"
|
||||
+++
|
||||
---
|
||||
title: "about me"
|
||||
path: "about"
|
||||
---
|
||||
|
||||
## matthew ess (they/them)
|
||||
i'm a 'software engineer'/'code monkey' by trade, currently employed by yelp inc in the engineering effectiveness department. my work is focused on improving the tooling used by other engineers at yelp to develop python services.
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
+++
|
||||
path = "posts"
|
||||
template = "posts.html"
|
||||
sort_by = "date"
|
||||
+++
|
||||
---
|
||||
path: "posts"
|
||||
template: "posts.html"
|
||||
sort_by: "date"
|
||||
---
|
|
@ -1,13 +1,13 @@
|
|||
+++
|
||||
title = "cellular automata toys in löve2d"
|
||||
date = "2022-09-15"
|
||||
description = "a short announcement post for a few interactive cellular automata toys written in lua"
|
||||
[taxonomies]
|
||||
tags = ["cellular-automata", "lua", "löve2d"]
|
||||
[extra]
|
||||
hero = true
|
||||
heroPrompt = "The oracle reading the future from Conway's Game of Life, technomancer aesthetic, digital illustration, 8k uhd"
|
||||
+++
|
||||
---
|
||||
title: "cellular automata toys in löve2d"
|
||||
date: "2022-09-15"
|
||||
description: "a short announcement post for a few interactive cellular automata toys written in lua"
|
||||
taxonomies:
|
||||
tags: ["cellular-automata", "lua", "löve2d"]
|
||||
extra:
|
||||
hero: true
|
||||
heroPrompt: "The oracle reading the future from Conway's Game of Life, technomancer aesthetic, digital illustration, 8k uhd"
|
||||
---
|
||||
|
||||
after reading [Andrew Healey's blog post about Langton's Ant](https://healeycodes.com/virtual-ants), i found myself inspired to reimplement some of his work. i've read numerous rave reviews of löve2d for writing simple toys, so i decided to give that a shot here as well. Langton's Ant went well enough that i also implemented Life and Wireworld.
|
||||
|
||||
|
|
|
@ -1,13 +1,13 @@
|
|||
+++
|
||||
title = "passing command line arguments to nix flakes"
|
||||
date = "2022-10-10"
|
||||
description = "a tutorial on 'breaking' the hermeticity of nix flakes by adding convenient command line flags"
|
||||
[taxonomies]
|
||||
tags = ["nix"]
|
||||
[extra]
|
||||
hero = true
|
||||
heroPrompt = "A rogue program hacking through the firewall, in the style of Tron Legacy, cyberpunk vibe, digital render, 8k uhd, unreal engine"
|
||||
+++
|
||||
---
|
||||
title: "passing command line arguments to nix flakes"
|
||||
date: "2022-10-10"
|
||||
description: "a tutorial on 'breaking' the hermeticity of nix flakes by adding convenient command line flags"
|
||||
taxonomies:
|
||||
tags: ["nix"]
|
||||
extra:
|
||||
hero: true
|
||||
heroPrompt: "A rogue program hacking through the firewall, in the style of Tron Legacy, cyberpunk vibe, digital render, 8k uhd, unreal engine"
|
||||
---
|
||||
|
||||
[Nix flakes](https://serokell.io/blog/practical-nix-flakes) are very useful, but the feature of a [fully hermetic build](https://bazel.build/basics/hermeticity) also means that they carry with them a certain degree of inflexibility. [Users have asked for a mechanism to parameterize flakes](https://github.com/NixOS/nix/issues/2861#issuecomment-891521971), but there seems to be no interest from the Nix maintainers in adding such a feature.
|
||||
|
||||
|
|
|
@ -1,10 +1,10 @@
|
|||
+++
|
||||
title = "diy code hosting with gitea and fly.io"
|
||||
date = "2022-08-07"
|
||||
updated = "2022-09-04"
|
||||
[taxonomies]
|
||||
tags = ["git", "gitea", "fly.io"]
|
||||
+++
|
||||
---
|
||||
title: "diy code hosting with gitea and fly.io"
|
||||
date: "2022-08-07"
|
||||
updated: "2022-09-04"
|
||||
taxonomies:
|
||||
tags: ["git", "gitea", "fly.io"]
|
||||
---
|
||||
|
||||
## Setting the Scene
|
||||
Inspired by the [Give Up Github campaign](https://sfconservancy.org/GiveUpGitHub/), I recently decided I wanted to spin up my own instance of [Gitea](https://gitea.io/). There are free (as in beer), free (as in freedom), public instances of Gitea and other FOSS-leaning code forges, but self-hosted Gitea struck me as a nice way to take even a bit more ownership over my own code.
|
||||
|
@ -50,14 +50,14 @@ mkdir gitea; cd gitea
|
|||
Next up, we create our app configuration and register it with Fly.io. `flyctl` takes care of this for us in a single command, `flyctl launch`. The command will prompt you interactively for some input, but here we'll just pass some flags directly:
|
||||
```bash
|
||||
flyctl launch \
|
||||
# use the official Gitea docker image \
|
||||
--image gitea/gitea:latest \
|
||||
# give our instance a unique name, this will be used to generate a development hostname like gitea-mat-services.fly.dev \
|
||||
--name gitea-mat-services \
|
||||
# region where the app runs, don't supply this option if you want to interactively choose a region \
|
||||
--region ewr \
|
||||
# don't immediately deploy, we need to edit our fly.toml first \
|
||||
--no-deploy
|
||||
# use the official Gitea docker image \
|
||||
--image gitea/gitea:latest \
|
||||
# give our instance a unique name, this will be used to generate a development hostname like gitea-mat-services.fly.dev \
|
||||
--name gitea-mat-services \
|
||||
# region where the app runs, don't supply this option if you want to interactively choose a region \
|
||||
--region ewr \
|
||||
# don't immediately deploy, we need to edit our fly.toml first \
|
||||
--no-deploy
|
||||
|
||||
# don't forget to commit!
|
||||
git add fly.toml
|
||||
|
|
|
@ -1,13 +1,13 @@
|
|||
+++
|
||||
title = "now on netlify"
|
||||
date = "2022-10-16"
|
||||
description = "a short update regarding me packing up my static site and moving from fly.io to netlify"
|
||||
[taxonomies]
|
||||
tags = ["static-site", "netlify"]
|
||||
[extra]
|
||||
hero = true
|
||||
heroPrompt = "A man packing up and leaving home to move to the city, luggage and boxes outside of his house, a moving truck idling in his driveway, gorgeous illustration, high quality art, masterpiece"
|
||||
+++
|
||||
---
|
||||
title: "now on netlify"
|
||||
date: "2022-10-16"
|
||||
description: "a short update regarding me packing up my static site and moving from fly.io to netlify"
|
||||
taxonomies:
|
||||
tags: ["static-site", "netlify"]
|
||||
extra:
|
||||
hero: true
|
||||
heroPrompt: "A man packing up and leaving home to move to the city, luggage and boxes outside of his house, a moving truck idling in his driveway, gorgeous illustration, high quality art, masterpiece"
|
||||
---
|
||||
|
||||
a short update today, and one that (unfortunately) obsoletes a lot of the work I put into [my last post on static site hosting](@/posts/static-site-with-nix-and-caddy/index.md): this site is now hosted on netlify! after [my most recent article](@/posts/command-line-flake-arguments/index.md) ran into some accessibility issues for people outside of my fly.io deployment region, I decided to minimize the moving parts involved in keeping the site running. i moved my static content over to [netlify](https://www.netlify.com/), a well-liked PaaS for deploying webapps and static sites (they also offer other things I don't care about, such as "Serverless" and FaaS offerings). [netlify's configuration file](https://docs.netlify.com/configure-builds/file-based-configuration/) supports all the same headers and redirects options that I was using in caddy, so the transition was extremely smooth.
|
||||
|
||||
|
|
|
@ -1,10 +1,10 @@
|
|||
+++
|
||||
title = "hosting a static site on fly.io with nix and caddy"
|
||||
date = "2022-09-04"
|
||||
updated = "2022-10-17"
|
||||
[taxonomies]
|
||||
tags = ["static-site", "nix", "caddy", "fly.io"]
|
||||
+++
|
||||
---
|
||||
title: "hosting a static site on fly.io with nix and caddy"
|
||||
date: "2022-09-04"
|
||||
updated: "2022-10-17"
|
||||
taxonomies:
|
||||
tags: ["static-site", "nix", "caddy", "fly.io"]
|
||||
---
|
||||
|
||||
**UPDATE**
|
||||
most of the information on this page is no longer accurate for my blog, [which has since moved to netlify](@/posts/now-on-netlify/index.md). it should still work, or get you close, but i recommend checking out [`nix-fly-template`](https://github.com/LutrisEng/nix-fly-template).
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "privacy notice"
|
||||
path = "privacy"
|
||||
+++
|
||||
---
|
||||
title: "privacy notice"
|
||||
path: "privacy"
|
||||
---
|
||||
|
||||
## summary
|
||||
i want to respect your pivacy, while still getting some insight into the readership of my site. no "personally identifiable information" or "sensitive information" is collected, and no data is shared with external parties.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "selected projects"
|
||||
path = "projects"
|
||||
+++
|
||||
---
|
||||
title: "selected projects"
|
||||
path: "projects"
|
||||
---
|
||||
|
||||
## gemini for rust
|
||||
`gemini` is a rust crate providing a small set of types useful for working with the Gemini protocol
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "resume"
|
||||
path = "resume"
|
||||
+++
|
||||
---
|
||||
title: "resume"
|
||||
path: "resume"
|
||||
---
|
||||
|
||||
## skills
|
||||
### professional
|
||||
|
|
Loading…
Reference in New Issue