From 83e88e911a2a9e64b401c7613c73ea3eeaa806cc Mon Sep 17 00:00:00 2001 From: Kasra Bigdeli Date: Mon, 2 Jul 2018 12:17:27 -0700 Subject: [PATCH] Deploy website Deploy website version based on 738b18511866aafae6055c5006219d09d9569848 --- docs/deployment-methods.html | 6 ++++-- en/index.html | 4 ++-- index.html | 4 ++-- 3 files changed, 8 insertions(+), 6 deletions(-) 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.

Deploy via Web Dashboard

-

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.

Deploy using Github, Bitbucket and etc.

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: