I believe I already mentioned to check this, but your build command is wrong. It was the first thing I asked. You are using npm and not pnpm. Look at the docs again.
The build command should be: npm install pnpm & pnpm install & pnpm run build
I don’t know at this point what issue i am facing. i can retry everything from step one but here is the images of the changes and it’s still not deploying properly.
@coderz What service are you talking about? Cloudflare Pages don’t use CPU or cost $5 per month. They are completely free. And they support only compiled static pages with Workers and Actions (for the dynamic pieces). On top of you can pass API’s to them, and they have integration for things like Supabase, databases, storage, etc. So, they can work like hosted solutions, but they are different.
Hey there. I’m not sure if it’s been mentioned or not. But the “Application Error” folks are seeing with X@https…, Mu@https… etc is related to Safari browsers. The application works fine in Chrome but not in any Safari based browser (desktop or mobile). Hope that helps.
Depends on what you mean, lol. Figuring out the steps, refining them, and then finally writing the documentation took several days and a bit of trial and error, especially because there was no good reference…
But the actual deploying with Cloudflare Pages actually only takes about 5 minutes (I can probably do it in ~2). It seems like a lot when scrolling through but it’s really just thorough with step-by-step instructions, and a lot of screenshots.
Follow it (read and follow every step) and you will be fine.
Dude. i freakin did, it took me days of warming up, but today, i took the videos and the your manual, after the 3rd retry it worked. and i sorted things out with stable and main, and where to delete and what to choose. So now im at the part, where my jaw is like dropped and im like, do i really have it? while im looking at the new homescreen…lol. So my question is…Do i need to get all these apis now? is that the game, get as many apis? or does this thing come fully packed and ready to go for free? im a little confused at this part here. Thank you for your response, relaly appreciate it! and of course all the work you and your partners have done. I got into coding because my crypto experience as a youtube, i always admired coders and developers on how they can build these smart contracts… so i have always wented to code and i ran into the main guy who create this forum, and it was the video where he was like, i forked it and may it better, at that time i just ran into bolt and tried it for free. so when i saw his video, i was like, wtf is this dude up too lol. So when i watched it, i knew i ran into something special, i felt a real buzz in the community and i have felt that in different avenures in crypto like for instance in a bullrun. But this is amazing, i hope to build and hope add some awesome ideas or suggestions that i can from my persepective as a non coder lol.
For paid I would recommend using OpenRouter, which has a lot of Models and also some very cheep ones.
Take a look on the FAQ, where some mentioned: https://stackblitz-labs.github.io/bolt.diy/FAQ/
Provider APIs are a tricky one. There are a lot of free options, it’s just a bit to manage them all.
For FREE, you can get: ChatGPT 4o and others through GitHub, Gemini Flash 2.0 (exp-1210) through Google AI Studio, HuggingFace (various), Ollama or LMStudio locally, and so many more I’m sure. You can even get Claude 3.5 for free, but it’s hacky. All have various rate limits and caps to various degrees.
I personally pay for Openrouter because it’s the best price and has so many models easily available. And it also has some free models, but I’ve had mixed experience with them. And I’ve been using DeepSeek-V3 (alias DeepSeek-Chat) and it’s really good but also super cheap.
Is there any way we can keep this deployment in sync with the new changes happening on the bolt.diy repo? I’d like it to be updated whenever the main repo has changes, or I can manually do it, but unsure of how to since we forked this.
However, I have setup a GitHub action to do this automatically and just keep the repo up to date on change, but I haven’t created documentation for it yet. It’s honestly not that hard either and just keeps me from having to do it manually.
Instructions have been updated with Troubleshooting steps for common issues and how to update your deployment when Bolt.diy gets updates.
Also, a TBD section was added with additional things I would like to write up, but as a whole this documentation should probably move somewhere where it can be split and cleaned up for an easier read (with say scroll sections, quick links, etc.)