search

denoland / deploy_feedback

For reporting issues with Deno Deploy
https://deno.com/deploy
74 stars 5 forks source link

Better support for monorepos #233

Open aabedraba opened 2 years ago

aabedraba commented 2 years ago

Currently, when having multiple deno projects in the same repository and all deployed in Deno Deploy they all get a deployment trigger when I commit to one of the folders. Is it possible to declare specifically what folder/projects should be deployed from a repository? Here's an example of a mono-repo I have https://github.com/aabedraba/dotcom

On the other hand, it affects the way relative paths work between local development vs deployment, because in local development your Deno.cwd() would be PATH_IN_FILESYSTEM/project-1 while in Deno Deploy it would be /src. For this case, I had to include a conditional to make this work in local development and production https://github.com/aabedraba/dotcom/blob/master/www/routes/index.tsx#L72-L78

ferbs commented 2 years ago

Looks like their deployctl tool offers more granularity than what's used by the default Github Action, but would require some .github/workflows customization, mapping each Deploy project to its mod.ts entrypoint and customizing the conditions/events desired to deploy a project independently.

Maybe the Deploy folks will provide examples though. I stumbled on a related request so we're probably not the only ones investigating the topic.

jvhellemond commented 4 weeks ago

Being able to specify a root path within a repository would be great. This could prevent changes outside this root from triggering a deploy. Netlify has this.