lee/caprover
1
0
Fork 0
mirror of https://github.com/caprover/caprover synced 2026-05-06 03:30:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update deployment-methods.md

Browse Source
This commit is contained in:
Kasra Bigdeli
2018-11-13 17:32:55 -08:00
committed by GitHub
parent 95dfceaf28
commit a80ebb2794
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment-methods.md
+1 -1
View File
@@ -19,7 +19,7 @@ Zip the content of your project into a tarball (`.tar`), go to your Captain web
This method is perhaps the most convinient one. This method automatically triggers a build when you push your repo to a specific branch (like `master` or `staging` or etc). To setup this, go to your apps settings and enter the repo information:
- github/bitbucket username(email address): This is username that will be used when Captain downloads the repo.
- github/bitbucket password: You can enter any non-empty text, like `123456`, for public projects.
- repo: This is the main HTTPS address of repo, in case of github, it is in `github.com/someone/something` format.
- repo: This is the main HTTPS address of repo, in case of github, it is in `github.com/someone/something` format. Make sure it does NOT include `https://` prefix and `.git` suffix.
- branch: The branch you want to be tracked, for example `master` or `production`...
After you enter this information, save your configuration. And go to your apps page again. Now, you'll see a new field call webhook. Simply copy this webhook to your github/bitbucket repo. Captain listens to `POST` requests on this link and triggers a build.