Skip to content

Commit

Permalink
update self-hosting README to include Cloudflare Account ID configura…
Browse files Browse the repository at this point in the history
…tion step
  • Loading branch information
dphuang2 committed Dec 6, 2024
1 parent f8b4373 commit a26197f
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions generator/konfig-next-app/self-host/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@
![domain done](domain-complete.png)
1. You need to ensure that the codebase includes a mapping of your domain to the github repo. Go to [generator/konfig-next-app/src/utils/domain-to-repo-mappings.ts](../src/utils/domain-to-repo-mappings.ts) and add your domain as a key and owner/repo as the value. Look at existing entries for examples.
1. The GitHub App ID also needs to be updated to the ID of the GitHub App you created earlier. Go to [octokit.ts](../src/utils/octokit.ts) and edit `APP_ID` at the top of the file with your app's ID. Again, you can use the GitHub edit UI to do this.
1. The Cloudflare Account ID also needss to be updated to be the ID of the Cloudflare account you created earlier. Go to [cloudflare-images-from-github.ts](../src/utils/cloudflare-image-from-github.ts) and replace the `account_id` variable with your own account ID.
1. Deploy `konfig-demo-portal` off latest commit. If you want, you can also enable auto-deploys if you don't want to manually click deploy anymore: https://render.com/docs/deploys#automatic-git-deploys.
![deploy](deploy.png)
1. Once your services are deployed correctly, which can take 30 minutes or more because its building the entire Konfig monorepo, you should be able to go to your custom domain and the docs should show.

0 comments on commit a26197f

Please sign in to comment.