The git plugin uses git running on the remote host to fetch the code of the app being deployed. This “remote pull” technique is currently the only deployment method officially supported by tomo. For this to work, the SSH key you use to connect to the remote host via tomo must match the key expected by the git host (e.g. by GitHub).
||The branch of the repository to deploy||
||Directory on the remote host where a cache of the repository will be stored||
||An array of paths (similar to gitignore syntax) that will be excluded when the repository is copied into a release; it is recommend you exclude
||Environment variables that will be set when issuing git commands (hash)||
||URL of the git repository; always use the SSH form like
Performs the initial clone of the git repository. This is necessary before a deploy can be performed. The clone of the repository will be stored in the
git_url setting must be specified for this task to work.
git:clone is intended for use as a setup task.
Fetches the latest commits from
git_branch and creates a release by copying the contents of that branch of repository into a new release inside the
releases_path. Releases are numbered based on the timestamp of when the deploy takes place.
git:create_release is intended for use as a deploy task.
remote.git(*args, **options) → Tomo::Result
git with the environment variables specified by the
remote.git("fetch") # $ export GIT_SSH_COMMAND=ssh\ -o\ PasswordAuthentication=no\ -o\ StrictHostKeyChecking=no && git fetch