This repo contains the code powering my personal website. Is uses markdown files written with Obsidian stored on the local file system along with Next.js to generate a static React site.
Make sure you have pnpm and the Node.js version
listed in the .node-version file installed locally. Then, you can use pnpm to do
everything else!
| Command | Action |
|---|---|
pnpm dev |
Starts a local dev server at localhost:3000 |
pnpm build |
Build the production site to dist |
pnpm lint |
Run the linter |
pnpm test |
Run the tests |
To see the other available commands, check the package.json file.
There are a few constraints that make deploying this repo a little more challenging than normal.
- First, Obsidian Sync does not provide an API for accessing the synced data. This means that I can't easily access the source content for this website in a CI environment.
- Second, GitHub Actions doesn't easily allow actions to be configured to run on a repeating basis on a free plan.
Given these limitations, I've decided instead to deploy on my personal laptop using the
deploy script scheduled via launchd. This require a bit of setup, but once it's
running it will always deploy the site daily.
Since this repo will be running on my local machine, it's important that a few preconditions are met in order for the deployment to work correctly.
- SSH must be configured to clone the repo and push up the deployment branch.
- The repo must be cloned to
$HOME/Development/landonschropp.comsolaunchdcan find thedeployscript. - The required environment variables must be set via an
.envrcfile. This deploy script will automatically load this file.
To manually deploy, run bin/deploy.
To set up launchd to automatically deploy, run:
launchctl load -w deploy.plistIf the plist has been previously loaded, you'll first need to unload it.
launchctl unload -w deploy.plist