TODOs / Notes to self

[coolaj86]

API Notes

Link to Dropbox Paper doc:
https://www.dropbox.com/scl/fi/54jpjeaqsl4xyddigehkp/git-deploy.paper?dl=0&rlkey=amfpoutjtzwozygvgb38h508s

list remote git tags

This may come in handy:

git ls-remote --tags git@bitbucket.org:ryanburnettecala/test.git

deploy vs access keys

• https://github.com/webinstall/webi-installers/settings/keys
• https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys

[coolaj86]

TODO

gitdeploy is intended for use with static websites that are generated after
changes are pushed to a Git repository. This works with sites that are being
edited in code and tracked in Git. Sites that have their content managed with a
headless CMS that pushes to Git are also very well-suited.

gitdeploy supports verified webhooks from Github, Bitbucket, and Gitea.

gitdeploy is written in Go. This means that it's a standalone binary
available on all major operating systems and architectures. It provides an API
with endpoints that handle webhooks, allow for initiation of builds, and getting
the status of builds and build jobs.

gitdeploy comes with a simple interface. The interface be disabled if you
don't want to use it.

gitdeploy also comes with basic authentication via integration with
Pocket ID. Authentication can also be disabled if you
don't want to use it. The built-in interface requires the built-in
authentication.