Auto saved by Logseq

This commit is contained in:
Daniel Gallegos 2023-08-12 18:35:31 -04:00
parent efc1d0039c
commit c780b7b54c
3 changed files with 5 additions and 4 deletions

View file

@ -1 +1 @@
["6819d5ac-7c6b-4965-ba7b-e56686e61416" "e11b5282-195e-40cb-af42-af79882dc719" 56]
["6819d5ac-7c6b-4965-ba7b-e56686e61416" "e11b5282-195e-40cb-af42-af79882dc719" 57]

View file

@ -1,7 +1,8 @@
public:: true
tags:: #seed #infrastructure #github #logseq sync
- i'm not changing the title.
- i'm not changing the title. long urls 5evr.
- did you know [[mastodon]] urls shorten down to like 32 characters? so this won't matter for my target audience lol
- # set up [[logseq]]
- or whatever your [[personal knowledge management]] tool of choice is.
- # create a new [[github]] [[repository]]
@ -33,5 +34,5 @@ tags:: #seed #infrastructure #github #logseq sync
- this will publish your page at `yourusername.github.io/yourrepository`. HOWEVER, you probably want custom dns stuff like i've got setup. so you need to...
-
- # set up the github repository for custom dns
- the
- your [[dns]] provider is gonna have a different setup depending on what their web interface looks like, so i can't help you too much here. but you're going to need a `CNAME` record that redirects to `yourusername.github.io`. that will point that url to github's servers so it will know what
-

View file

@ -34,5 +34,5 @@ tags:: #seed #infrastructure #github #logseq sync
- this will publish your page at `yourusername.github.io/yourrepository`. HOWEVER, you probably want custom dns stuff like i've got setup. so you need to...
-
- # set up the github repository for custom dns
- your [[dns]] provider is gonna have a different setup for every
- your [[dns]] provider is gonna have a different setup depending on what their web interface looks like, so i can't help you too much here. but you're going to need a `CNAME` record that redirects to `yourusername.github.io`. that will point that url to github's servers so it will know what
-