4 ms·
IMO, one of the coolest features of Deno Deploy is that the deployment primitive is the humble URL, rather than being coupled to git or some git hosting provide
by eins1234 5y ago
IMO, one of the coolest features of Deno Deploy is that the deployment primitive is the humble URL, rather than being coupled to git or some git hosting provider.
You can simply give it a URL to a JS file and it will fetch all its dependencies and run it. They also offer an API for triggering deploys programmatically [1], which you can use to trigger deploys as a step in your CI pipeline for GitLab.
In fact, their GitHub integration is actually just listening for a webhook on new commits to the default branch, and the deploy is triggered using the raw.githubusercontent.com URL, so they don't have to waste time cloning the entire repository, which can save on the order of minutes for large repos. [2]
[1] https://github.com/denoland/deploy_feedback/issues/29#issuecomment-863116023 https://github.com/denoland/deploy_feedback/issues/29#issuec...
[2] https://github.com/denoland/deploy_feedback/issues/29#issuecomment-836662805 https://github.com/denoland/deploy_feedback/issues/29#issuec...
- tqkxzugoaupvwqr 5y agoIf I read this correctly, the repository has to be public so Deploy can fetch the code. Or does it work with private GitLab repos?
- eins1234 5y agoI'd imagine you could probably issue some access token in GitLab for Deno deploy to fetch the code. Deno deploy works with private _GitHub_ repos and I imagine that's basically what they do there. Alternatively, you could also just set up a CI script to upload your code to a random s3 bucket, call the deploy API, then delete it if you want to minimize the chance of leaking.