3 ms·
My preferred way to deploy my websites is to push the changes to git and have a web hook handle a deployment. I don't see anything about web hooks being support
by alias_neo 3y ago
My preferred way to deploy my websites is to push the changes to git and have a web hook handle a deployment. I don't see anything about web hooks being supported, that'd be pretty nice since version control is pretty much a non-negotiable, zero extra steps is the winner.
- antoniomika 3y agoWe don't presently have webhooks, but do have a GitHub action for this (https://github.com/marketplace/actions/pgs-action https://github.com/marketplace/actions/pgs-action). The goal was to make it easy to deploy using off the shelf tools and not require anything to be installed for usage. I could see us thinking about making this a feature/addon down the road.
- alias_neo 3y agoThe Github action is probably good enough if one is happy/willing for Github to hold the SSH private key to access their site. I see your point about not wanting to add extra tools; can I ask what you use for serving the sites? I've used things like Caddy server in the past to do things like generating the static site from my Markdown with Hugo, but I currently use "Apps" on Digital Ocean which uses web hooks to detect commits and deploy my Hugo static sites.
- antoniomika 3y agoWe do use Caddy, but just for reverse proxying and handing TLS. We utilize custom http/ssh servers on the backend to handle everything. All of our work is open source and we do development in the open / discuss features over IRC on Libera. You could self host pgs if you wanted! Here's the repo: https://github.com/picosh/pico https://github.com/picosh/pico
- alias_neo 3y agoThanks for the info, that's really cool to hear! I'll check it out.
- sdf4j 3y agowhy a web hook though? you can use a git post commit hook and run the deployment steps without adding more moving parts and complexity.