Combine tips with blog
Still should 301 the old URLs or something
This commit is contained in:
parent
1a90ac8620
commit
b4d021b22a
10
config.yaml
10
config.yaml
|
|
@ -19,7 +19,7 @@ markup:
|
|||
# post: /blog/:title
|
||||
|
||||
params:
|
||||
Description: "Hi! I'm Daniel. I live in Kansas City where I help run a small Christian church, raise two kids with my awesome wife, and write software for Divvy."
|
||||
Description: "Hi! I'm Daniel. I live in Kansas City where I help run a small Christian church, raise three boys with my awesome wife, and write software."
|
||||
|
||||
outputs:
|
||||
home: [html]
|
||||
|
|
@ -35,10 +35,10 @@ menu:
|
|||
name: blog
|
||||
url: /blog/
|
||||
weight: 20
|
||||
- identifier: tips
|
||||
name: tips
|
||||
url: /tips/
|
||||
weight: 30
|
||||
# - identifier: tips
|
||||
# name: tips
|
||||
# url: /tips/
|
||||
# weight: 30
|
||||
- identifier: contact
|
||||
name: contact
|
||||
url: /contact/
|
||||
|
|
|
|||
|
|
@ -7,19 +7,22 @@
|
|||
<!-- updates here must be mirrored in site config for meta description-->
|
||||
|
||||
I live in Kansas City where I help run <a target="_blank"
|
||||
href="https://kcrising.church">a small Christian church</a>, raise two kids
|
||||
href="https://kcrising.church">a small Christian church</a>, raise three boys
|
||||
with my <a target="_blank"
|
||||
href="https://www.instagram.com/valerielauren93">awesome wife</a>, and write
|
||||
software for <a target="_blank" href="https://getdivvy.com">Divvy</a>.
|
||||
software for <a target="_blank" href="https://getdivvy.com">Divvy (bought by
|
||||
Bill.com)</a>.
|
||||
|
||||
I run a ton of self-hosted software here at home on some machines that sit on
|
||||
I run a lot of self-hosted software here at home on some machines that sit on
|
||||
[an unnecessarily large server rack in my basement][rack]. I love building
|
||||
[keyboards][kb], too. [I heavily customize my workflow][wf] and you can
|
||||
sift through my [dotfiles][df] if you like.
|
||||
see how I set everything up with [Nix][nix] if you like (or even my old
|
||||
[dotfiles](df)).
|
||||
|
||||
Occasionally, I post technical articles here.
|
||||
Occasionally, I post technical articles (of varying length and complexity) here.
|
||||
|
||||
[rack]: //files.lyte.dev/images/server-rack.jpg
|
||||
[rack]: //files.lyte.dev/images/server-rack-angle-2023-07.jpg
|
||||
[kb]: //files.lyte.dev/keyboards
|
||||
[wf]: //files.lyte.dev/images/desktop-screenshot.png
|
||||
[wf]: //files.lyte.dev/images/desktop-screenshot-busy-2023-07.png
|
||||
[nix]: //git.lyte.dev/lytedev/nix
|
||||
[df]: //git.lyte.dev/lytedev/dotfiles
|
||||
|
|
|
|||
|
|
@ -1,12 +1,14 @@
|
|||
---
|
||||
title: "Fetching Go Modules via `goproxy` Inside VPN"
|
||||
date: "2023-06-22"
|
||||
date: "2024-02-29"
|
||||
---
|
||||
|
||||
I think I finally setup the holy grail of universally being able to
|
||||
fetch-by-proxy go modules through a firewall using
|
||||
https://github.com/goproxy/goproxy
|
||||
|
||||
<!--more-->
|
||||
|
||||
On your internal host (such as your work machine), run the following:
|
||||
|
||||
```shell_session
|
||||
|
|
@ -6,6 +6,8 @@ date: "2023-06-22"
|
|||
I love `iex -S mix ...` but I usually don't like when `dbg` asks me to `pry`.
|
||||
Just show me my data! Well, today I learned about `iex --no-pry`:
|
||||
|
||||
<!--more-->
|
||||
|
||||
```console
|
||||
$ iex --help
|
||||
Usage: iex [options] [.exs file] [data]
|
||||
|
|
@ -15,4 +17,4 @@ Usage: iex [options] [.exs file] [data]
|
|||
|
||||
Now I can `iex --no-pry -S mix ...` and just see output instead of dealing with
|
||||
the prompts for `pry`ing! Not sure if anybody else felt this pain, but there
|
||||
ya go.
|
||||
ya go.
|
||||
|
|
@ -5,6 +5,14 @@ draft: true
|
|||
toc: false
|
||||
---
|
||||
|
||||
For the longest time, my backup setup has been [a script I run manually that
|
||||
was quite dumb][backupify] that had no features other than encryption. After
|
||||
getting my feet wet with `btrfs` somewhat recently and seeing the magic of
|
||||
deduplication, compression, and snapshots, I was all-in on these features and
|
||||
also wanted them for my backups.
|
||||
|
||||
<!--more-->
|
||||
|
||||
# TL;DR
|
||||
|
||||
- Install `restic` on both machines (may only be needed on the backupper?)
|
||||
|
|
@ -14,18 +22,6 @@ toc: false
|
|||
password in a secret place accessible only to the backupper user
|
||||
- `for d in $DIRS; do RESTIC_PASSWORD_COMMAND="load secret restic-key" restic -r sftp:restic@backuppee:/backups "$d"; done`
|
||||
|
||||
<!--more-->
|
||||
|
||||
# Intro
|
||||
|
||||
For the longest time, my backup setup has been [a script I run manually that
|
||||
was quite dumb][backupify] that had no features other than encryption. After
|
||||
getting my feet wet with `btrfs` somewhat recently and seeing the magic of
|
||||
deduplication, compression, and snapshots, I was all-in on these features and
|
||||
also wanted them for my backups.
|
||||
|
||||
I also had a friend that had been using `btrfs` snapshots for sometime and I was super impressed with the simplicity of his setup. It made me want to improve mine!
|
||||
|
||||
# Planning
|
||||
|
||||
The most important thing to think about when it comes to backups is to think
|
||||
|
|
|
|||
|
|
@ -1,5 +0,0 @@
|
|||
---
|
||||
title: Blog
|
||||
---
|
||||
|
||||
## Latest Tips ([RSS](/tips/index.xml))
|
||||
|
|
@ -16,18 +16,4 @@
|
|||
{{ end }}
|
||||
</details>
|
||||
|
||||
<details open>
|
||||
<summary>
|
||||
<h2 id="latest-tips">
|
||||
Latest <a href="/tips">Tips</a> (<a target="_blank" href="/tips/index.xml">RSS</a>)
|
||||
</h2>
|
||||
</summary>
|
||||
|
||||
{{ range (where .Site.RegularPages "Section" "tips") }}
|
||||
{{ .Render "li" }}
|
||||
{{ else }}
|
||||
<p>Looks like there's nothing here!... yet!</p>
|
||||
{{ end }}
|
||||
</details>
|
||||
|
||||
{{ end }}
|
||||
|
|
|
|||
Loading…
Reference in a new issue