Cloudflare Deployment running only one
I can only run one Cloudflare deployment I wish to run 4
33 Replies
?pings
Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
Oh
I'm so sorry
You need to upgrade your plan
I won't do it in the future thank you for letting me know
Assuming that's even what you're talking about, feel free to clarify if not
Oh
I don't have money to pay, (Living home) So I'll try some other options, thx for the help
I'll ask Bota Apex As it's there site
And not mine
Can I use Cloudflare worker? to host multiple Github repository's
I invited Bota Apex they will mostly come later
You can still create multiple projects 🙂
What limit are you running into exactly here? I feel there may have been a misunderstanding
Still not sure what the issue is. What issue are you hitting?
You can have unlimited projects and have unlimited sites.
What is preventing you from having a second or x amount? What error? Where are you seeing it?
Also is this making a project? Adding a domain? What part is failing?
What do you mean by a deployment? Could you answer the questions Walshy shared?
You mean you can only have one deployment building at the same time?
Please don't ping me in every reply by the way, I am active here 🙂
Ah then that would be dependant on your plan level, and creating additional accounts to bypass limits would not be allowed
You can have unlimited websites and unlimited live deployments, you just cannot build more than one at once đź‘Ť
@HOLDULV ?
Bota Apex Support:
We are working on a solution please allow us to find it
Is this the support?
We are still trying to find a solution to hosting If it's Cloudflare or another service, We don't know yet
But we Love your support
Please, do not ping directly. And especially don’t retract it after the fact.
?pings
Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
You were told already. In this thread.
Do I really need to repeat the “please don’t ping again”?
That question was asked already, Erisa will reply when and if she gets to it. Repeating the question will definitely not help. Not is pinging again by replying to the message.
The limit here is Pages builds, not how many Pages websites you can have - nor how many Workers you can have.
You can host 4 different repositories without needing a Worker.. you can have unlimited websites linked to however many github repositories you want
Just add them. You can only build at a time concurrently. You can build 100s just not at the same time, they will be sequentially built.
Just create more projects
And you can, just add the projects separately without any issue.
Cloudflare Pages hosts websites, not bots
No, there can only be 1 build running at a time, so if you push a new commit to each project they will all build just fine, just one after the other and not at the same time.
But, why?
Each project is independent... and it's free. Just host all and wait the few minutes it takes to build it. Are you really pushing updates to all projects all the time at the same time?
As far as I can tell here, there is nothing to work around.
What are you trying to host on Cloudflare pages?
Pages is not for hosting long-running programs like bots, if you use it for this you will get banned.
Why do you need more than 1 build? It's supposed to build the files for your site and that's it, it shouldn't take more than a few minutes.
If you're running a server in the build environment, that's a mis-use of it and that's why this thread has been confusing.
If you want to run server-side logic for your website, you'd use Pages Functions which are basically Cloudflare Workers - they're not NodeJS and you likely can't run something like Strapi on them.
You can make 4 sites without 4 concurrent builds
We're still unsure why you need 4 concurrent builds and how Workers would solve that
The question is still relevant.
We aren't understanding why you need 4 builds.
And the Pages build image is not meant for hosting bots.
It's meant for building (static, non-Express) websites.
If you are using it to host a bot you are in violation of the Terms of Service of Pages.
Not on Pages build images.
A service like fly.io would work, or Railway.
But the Pages build image should not be used to run bots.
If it's completely static then yes, you can run on Pages. But even then you cannot run in the build image.
You need to actually build your site in the build image and then allow Pages to deploy it.
And if it uses Express then it cannot be run at all.
You don't run it. Pages will run it for you.
You need to output static HTML or JS.
You do not run a server, Pages will do that for you.
That is your issue then. Cloudflare Pages cannot run a Strapi server (which uses Express).
It can only run static websites or websites that can be run using Cloudflare Workers/Pages Functions.
with the Strapi API on RenderThe Strapi API is not running on Cloudflare Pages. The Strapi frontend is, not the server. OK, so then if you are outputting static content (the Strapi frontend) then Pages should deploy it fine? You should not be using Cloudflare Tunnel or otherwise running the server yourself. You need to run
gatsby build and then allow Pages to deploy the build folder.
(according to that article)
Why?
Custom Domains do not use npm tunnel or any other tunnel with Cloudflare Pages.
If you mean a custom domain for the API then that's completely different from Pages.
But Pages doesn't need a tunnel of any kind.
You don't need a tunnel for deploy on Pages. You don't need to expose localhost.
It seems you are trying to run the frontend yourself. You shouldn't be.
You should be simply building the assets, and that's it.
Pages will do the rest.
Run your build command, like npm run build, and then just leave it.
Pages will automatically scan your folder and deploy the built assets.
Any JS that's being built is designed to run in the browser, you shouldn't need to touch anything related to IPs at all.
You should build the output, let Pages deploy it, and then connect Custom Domains on the Pages dashboard.
No tunnels, no localhost, and no dealing with IPs.
That's what I'm saying. You should not use localhost.
It will run automatically.
You need to build it and then leave it so that the automated systems can run it for you.
It doesn't matter whether you followed the guide or not, the steps you need to take are the same regardless.
1. Create a Pages project.
2. Set your build command to gatsby build and your output directory to /public
3. That's it, you are done. Just push to github and it will be deployed.Sorry, I meant /public. Like in this screenshot.
Then you need to change it to
/public
It doesn't matter what database you used. You still need to change it to /publicWe are happy to see your finding ways to workaround systems
We will
And?
Fine
we are wroking on a solution
We won't
We are working on a solution, and it's not tested yet
If you want to suggest anything please contact our support
With experience you learn, stop putting all the weight on your shoulders
It's good, Do not worry
holdulv is gone?
bruh he didn't read the rules
did he
So from holdulv I should say: Thanks for your help, now the Bota Apex site can finally be up.
?pings
Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
oh we didn't know
thank you for letting us know
Do we close this
or?
If it's solved, I'll mark it as such.
We guess it's solved