deploy_feedback

Wonderful!!! I wanted to provide a Live Demo, I tried with Deno Deploy, but I got a brick wall there because of some unintended blocker (ironically haha): https://github.com/denoland/deploy_feedback/issues/802 My next best choice was to extend the support to Bun, and then deploy it with Render.com: https://fullsoak.onrender.com/ I wasn't aware Glitch can also support Deno. So, sincere appreciations for your Glitch example <3 <3

One of the biggest annoyances with Deno deploy/functions is that there is no way to store any data. This would be very useful to e.g. cache an auth token, store a key/value pair, etc. See also: https://github.com/denoland/deploy_feedback/issues/110 Is any work being done to fix this? Or is this out of scope currently?

It's my understanding that GFM is already easy to do, in fact there's an example of using it with Fresh in the fresh repository as it's used for the docs! https://github.com/denoland/fresh/blob/main/www/routes/docs/... Using MDX is a little trickier as the .mdx file needs to be compiled to a javascript file which is then interpretted. When running Deno yourself this isn't hard as you can use a dynamic import, but if you're planning on using Deno Deploy you'll be out of luck as it doesn't support dynamic imports currently. https://github.com/denoland/fresh/issues/640 Deno Deploy has an open issue asking for support if you want to give it a star. ;) https://github.com/denoland/deploy_feedback/issues/1 As a workaround, you can always setup a watcher and preprocess MDX files before deploying to Deno Deploy, but that seems against the spirit o

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#issuec... [2] https://github.com/denoland/deploy_feedback/issues/29#issuec...