Skip to content

Commit 24e90b4

Browse files
author
dphuang2
committed
add more
1 parent d1273f0 commit 24e90b4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

generator/konfig-next-app/self-host/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@
2222
Once its complete, you should see the domain show as `Verified` and `Certificate Issued`.
2323
![domain done](domain-complete.png)
2424
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.
25-
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.
26-
1. Deploy `konfig-demo-portal` off latest commit
25+
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.
26+
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.
2727
![deploy](deploy.png)
2828
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 commit comments

Comments
 (0)