-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update kintohub documentation with kintohub V1 deployment #27016
Conversation
Hey @ascorbic, |
docs/docs/deploying-to-kintohub.md
Outdated
|
||
## Deployment Configuration | ||
3. Grant the permission needed for accessing the repo that we created in the previous step. Or if you prefer not to connect your GitHub account, you may select **Import URL** and provide your access token. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per the Style Guide, docs should use "you" instead of "we".
3. Grant the permission needed for accessing the repo that we created in the previous step. Or if you prefer not to connect your GitHub account, you may select **Import URL** and provide your access token. | |
3. Grant the permission needed for accessing the repo that you created in the previous step. Or if you prefer not to connect your GitHub account, you may select **Import URL** and provide your access token. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to open this PR! Left some suggestions for improvements. It also looks like there are some merge conflicts. Once those are all resolved we can get this merged. Thanks for your contribution! 💜
docs/docs/deploying-to-kintohub.md
Outdated
|
||
You can configure additional features directly from your Project page. | ||
If you're not already there, select **Projects** on the left-hand navigation bar, and then click on the project you want to configure. | ||
4. Configure the service. Add the build command `yarn && yarn build` This command is actually doing the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Configure the service. Add the build command `yarn && yarn build` This command is actually doing the following: | |
4. Configure the service. Add the build command `yarn && yarn build`. This command is actually doing the following: |
docs/docs/deploying-to-kintohub.md
Outdated
- Install the dependencies | ||
- Run the gatsby build | ||
- Generate the contents to `./public` which is the default value of “Build Output Path” |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Install the dependencies | |
- Run the gatsby build | |
- Generate the contents to `./public` which is the default value of “Build Output Path” | |
- Install the dependencies. | |
- Run `gatsby build`. | |
- Put the generated site into the `./public` directory, which is the default value of “Build Output Path”. |
docs/docs/deploying-to-kintohub.md
Outdated
|
||
Wait for the deployment to be successful. | ||
Refresh the page, your website is now protected. | ||
6. Once the deployment is finished you can close the release logs, check the **Access tab** and copy the url there. Paste it to the browser and you will see your website is live! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
6. Once the deployment is finished you can close the release logs, check the **Access tab** and copy the url there. Paste it to the browser and you will see your website is live! | |
6. Once the deployment is finished you can close the release logs, check the **Access tab** and copy the URL there. Paste it to the browser and you will see your website is live! |
docs/docs/deploying-to-kintohub.md
Outdated
2. Enter your domain or subdomain you wish to map to your service | ||
3. Click **Add Domain** | ||
4. Follow the instructions to add a **CNAME** key and value to your DNS host provider | ||
5. Click **OK** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Enter your domain or subdomain you wish to map to your service | |
3. Click **Add Domain** | |
4. Follow the instructions to add a **CNAME** key and value to your DNS host provider | |
5. Click **OK** | |
2. Enter your domain or subdomain you wish to map to your service. | |
3. Click **Add Domain**. | |
4. Follow the instructions to add a **CNAME** key and value to your DNS host provider. | |
5. Click **OK**. |
Hi @bappr 👋 Can you solve the merge conflict and address the change requests? |
Description
KintoHub released their new version and the doc needs to be updated.