diff --git a/docs/deployment-methods.html b/docs/deployment-methods.html index b53e24f..2fb796e 100644 --- a/docs/deployment-methods.html +++ b/docs/deployment-methods.html @@ -10,7 +10,7 @@ Regardless of your deployment method, make sure that you have a 'captain-definit
Simply run captainduckduck deploy in your git repo and follow the steps. This is the best method as it's the only method that reports potential build failures to you. Read more about it here:
Get Started - Step 4.
Zip the content of your project into a tarball (.tar), go to your Captain web dashboard and upload the tar file.
Zip the content of your project into a tarball (.tar), go to your Captain web dashboard and upload the tar file. This deployment method is typically used for testing purposes only.
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:
push event.