From f36a5963449652cef3391801ec6ed8b2a60574d3 Mon Sep 17 00:00:00 2001 From: Kyle Kemp Date: Sat, 22 Jun 2024 23:32:44 -0500 Subject: [PATCH] update readme for setup instructions --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index bb4f757..62ec1a0 100644 --- a/README.md +++ b/README.md @@ -20,6 +20,7 @@ Check out the [contributing guide](CONTRIBUTING.md) for more information. 1. Figure out where you want to dump your content. It should be either a fork of [this repository](https://github.com/LederCards/cards), or at minimum the output should be formatted the same as that repository. 1. Change `https://ledercardcdn.seiyria.com` to your desired URL. At this time, it can't be changed easily in one place, so a find+replace all will be necessary. The `cards` repository will also need a [script update](https://github.com/LederCards/cards/blob/master/scripts/build-card-data.ts#L20) to change the base URL of the images. +1. Make sure you have a `NETLIFY_AUTH_TOKEN` and `NETLIFY_SITE_ID` set per repo so they have somewhere to deploy to, if you want to use netlify. 1. If you're me (@seiyria), you're going to want to have two netlify apps set up for deployment. You'll want to configure those, the domains for those, as well as update any URLs in the GitHub actions workflows. 1. Make sure DNS entries exist for both applications. -1. Update the `cards` repo action to point to the new `Library` repo for cross-building. +1. Update the `cards` repo action to point to the new `Library` repo for cross-building. You'll also need a PAT with `repo` scope enabled, and added to `CROSS_REPO_UPDATE_PAT`.