Monorepo deploy to to Netlify
- Dominant language
- TypeScript
- Stars
- 282
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Hey Ben,
I'm not sure where exactly to post this or if it's still relevant. Though I remember in some recent video I watched (not sure if codeponder or something else), you were talking about deploying monorepo frontend to Netlify and experienced some issues where you had to clear cache or something.
In case you still have the same issue, I found out that you need to create a `netlify.toml` file in the root directory and override some things to avoid the issue. I came across it through this article on [dev.to](https://dev.to/mikeeus/deploying-angular-and-lucky-monorepo-using-netlify-and-heroku-2efg). Check the section of **Configuring Base Directory**.
They also talk about it in the Netlify docs, thought it's a bit hidden. [Check it here ](https://www.netlify.com/docs/continuous-deployment/#deploy-contexts)
Anyway, if you are still having the Netlify issue, this might solve it. If I'm too late, maybe it can still be helpful for someone else.
Cheers!
(Awesome videos and hope you get back to Codeponder livestreams soon)
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the root-level netlify.toml approach described in the linked dev.to article, especially its Configuring Base Directory section, and compare it with Netlify's deploy-context documentation. Done means determining whether this repository still needs deployment guidance or configuration for its monorepo frontend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular
- Domain
- cloud, devops
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100