Feedback
Current Behavior
When using the “Share application” button on the dashboard to deploy a repository, the following issues occur:
-
For Monorepo projects (e.g.
https://github.com/enpitsuLin/skland-daily-attendance
), the deployment fails with the error:“Could not find a wrangler.json, wrangler.jsonc, or wrangler.toml file in the provided directory.”
-
However, when manually forking the repository and importing it (or importing a self-owned repository) with the Root directory set to
/apps/cloudflare
, the deployment works successfully without checking for wrangler configuration files in the root directory.
Questions
- Is a wrangler configuration file in the root directory a mandatory requirement for repository imports?
- How can we achieve the same successful deployment using the deploy button?
- Should we skip the wrangler.jsonc check?
- Or would it make more sense to perform the check after setting the Root directory?
Suggested Improvement
The deployment process should be more flexible to accommodate Monorepo structures by:
- Allowing users to specify the Root directory before checking for configuration files
- Or implementing a more intelligent configuration file detection that can traverse subdirectories