hazeezet/CapRover action

Deploy to caprover server with complete flexibility

Trust Signals

workflow.ymlSHA-pinned

uses: hazeezet/caprover-action@826a214b93ece3ec8ace20a101b0c85f7423fdb5 # v2

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
server	CapRover admin panel URL. Example: https://root.domain.com	yes	—
app-token	CapRover app token.	yes	—
app-name	Application name on the CapRover server. Your app must exists.	yes	—
registry-host	Your docker registry url Example: registry.gitlab.com/username/caprover-docker-images. this is used to store image temporarily before deploying	no	""
registry-user	Docker registry token.	no	""
registry-token	Docker registry token.	no	""
registry-name	Registry server to deploy to, only AWS and caprover registry is currently supported	no	caprover
aws-account-id	Your AWS account ID	no	""
aws-access-key-id	Your AWS access key	no	""
aws-secret-access-key	Your AWS secret access key	no	""
aws-region	Your AWS region of the registry	no	""
caprover-password	your caprover password, set this if you are deploying image to AWS, https://github.com/caprover/caprover/issues/1476	no	""
plain	If you are deploying plain files	no	false
tarfile	If you are deploying tar file	no	false
branch	If you are deploying plain files then set the branch name to deploy	no	main
content	Project folder path or tar file to use to create the image or upload	no	""
dockerfile	Docker file path of your project	no	""
image-name	Image name in your registry	no	""
image-tag	New image tag	no	latest
deploy-app	Deploy newly pushed image to caprover	no	true
build-platforms	Platforms to build the image for	no	linux/amd64

no outputs