I have a lot problems with builds with this "internal error" too.
I have 2 websites, both gatsby
I tried both:
1) gatsby build
2) fully static files (gatsby build on my local computer) and only public dir added to github repo
Websites 10.000 files and 13.000 files
(small files 1kB to 300kB) html, css, js, png and webp
Sometimes my build is succefull for this 10.000 files website - like 1 of 5 tries
But most build tries fail when deploying:
06:58:47.583 Finished
06:58:48.061 Deploying your site to Cloudflare's global network...
07:18:07.790 Failed due to an internal error
It would be great to add "clean urls" - removing trailing slash for directory urls, like in firebase:
```
"hosting": {
// ...
// Removes trailing slashes from URLs
"trailingSlash": false
}
```
I have also a lot of problems with builds.
I tried 2 ways od deploying static pages to Cloudflare:
1) gatsby build
2) fully static page (gatsby build on my local computer and push "public" dir to github repo
both ways are generating error:
08:35:00.770 Finished
08:35:01.232 Deploying your site to Cloudflare's global network...
08:54:16.759 Failed due to an internal error
it looks like a hidden limit - build timeout 20 minutes?
My website has 13000 small files (html, js, css, png, webp - max file size is about 300kB)
and I cant deploy it because of this error
I even limited image sizes from 1600px to 800px, and limited files to about 10000 files and still I get error
I have another website with 11000 files and I use "gatsby build" - and build is successful for 1 of 5 tries...
I have 2 websites, both gatsby I tried both: 1) gatsby build 2) fully static files (gatsby build on my local computer) and only public dir added to github repo
Websites 10.000 files and 13.000 files (small files 1kB to 300kB) html, css, js, png and webp
Sometimes my build is succefull for this 10.000 files website - like 1 of 5 tries But most build tries fail when deploying: 06:58:47.583 Finished 06:58:48.061 Deploying your site to Cloudflare's global network... 07:18:07.790 Failed due to an internal error
it looks like timeout after 20 minutes.. :(