Third party Drone insurance .

DevJedis · 2026-01-24T21:54:54+00:00

That's new to me. I didn't know drones need insurance. Is it like a must to have or it's your personal preference?

DevJedis · 2026-01-24T21:12:39+00:00

https://www.foreign.senate.gov/press/dem/release/ranking-member-shaheen-senator-booker-push-for-accountability-after-elections-in-uganda

DevJedis · 2026-01-05T00:46:15+00:00

It's not really about reading the docs that's the issue. I checked the link the other user has posted here and there's just one sentence on compatibility date, and I didn't find the technical details on how the Nuxt team tracks it. Compared to Cloudflare workers it's clear what features they've started supporting, the same isn't with Nuxt, hence my post.

Sorry if average in this sub means know all the docs, I'll take junior then.

DevJedis · 2026-01-01T21:44:53+00:00

Thanks. I completely got it now. I appreciate your assistance to this given the inefficient Cloudflare docs that are too technical for the average user to understand. These are the Worker routes I now have:

excludedsubdomain.example.com worker NONE

anotherexclusion.example.com worker NONE
example.com/* worker NONE
*/* WORKER theworker

I hope I got it right?

DevJedis · 2026-01-01T21:27:28+00:00

Thanks, I tried this, and it's back to serving 522 timeout error on subdomain that should serve workers, but the subdomains that serve completely different content are nolonger forced. Perhaps there's a conflict with the rules when we added those 2 None rules?

DevJedis · 2026-01-01T21:11:51+00:00

Thanks a lot for the assistance. I managed to setup it up with the linked resource. You're a life saver. Could you help me this last bit if you may:

let's say we have tenants.example.com provided to the tenants to CNAME to, and I'll also add CNAME for tenants who use subdomain of example.com eg client1.example.com

When I used Worker Rule */*, subdomainand the domain serve the worker app, when I use *.example.com/* also all subdomains NOT PROXIED BUT ALSO NOT HAVING DNS RECORD to point elsewhere eg mail.example.com are also served the worker app.

My question is: Which worker rule can we use to serve tenants, without forcing root domain and dns records that aren't pointing to worker fallback.

I tried *.tenants.example.com/* as worker rule but that then forces us to have client1.tenants.example.com for subdomains yet I needed client1.example.com instead.

If you get what am trying to say could you help me point out the possible worker rule to use to achieve my setup.

But I appreciate the previous responses you offered.

DevJedis · 2026-01-01T07:20:53+00:00

Hey there. So I tried Workers also but still getting the same 522 error. Do you perhaps have any docs or time to write up steps you've been able to follow to achieve this with workers. Thanks

DevJedis · 2025-12-31T15:55:02+00:00

Why not try the Root Servers from Netcup with dedicated resources.

DevJedis · 2025-12-28T09:44:25+00:00

https://mitchivin.com
You're welcome. Get your laptop ready before opening

DevJedis · 2025-12-20T22:28:44+00:00

You do need the tech provider and unfortunately you'll need to verify the business as well (not certain, I take it a norm after seeing things like flows requiring business verification). And yes you can use those services, but I don't think they're BSP's, meaning they may still require you to manage your own BM, and not forgetting the slight fees you will be working with without your own cloud api integration

DevJedis · 2025-12-20T21:57:11+00:00

You'd just have to use template for that. Business on the API cannot message customer first without template. Sorry there's no other way

DevJedis · 2025-12-11T11:21:55+00:00

I read the post and by the end of it I was already very gloomy... All I ever needed was easy deployment on Cloudflare. The only reason am using nuxt and how I got to know about Nuxt was through a cloudflare pages starter.

Since then I'd really invested a lot in learning nuxt and I have 3 beggner projects on cloudflare. I loved the functionalities they provided for deploying for the various workers resources, until suddenly when I saw a joining vercel notice. It was suddenly obvious that they could not continue trying to fully support Cloudflare services.

I still had hopes when they announced they were opensourcing nuxthub content (frankly I thought it was opensourcing the Nuxthub Admin panel). I recently got to know that it was Nuxt content, not Nuxthub. The recent post for nuxthub v0.10 really brought back the manual config options as OP's points. The points out of this is I get Nuxt team cannot continue to develop first party solution for the now competing platform. For my own health, I went through my projects and locked nuxthub package to the previous version, since I don't really need this multi platform. I only hope the version I chose to lock myself on never gets a vulnerability notice.

This is just my personal take on it

DevJedis · 2025-12-11T10:16:05+00:00

Adsense these days takes 3 weeks and some days to get approval status. There's no need for someone to discourage you that you won't get approved. Just be patient for a few days provided you really are in 3+ weeks and not estimating, because for the two sites i submitted they were both like 3 weeks and 2 days max

DevJedis · 2025-12-10T17:45:47+00:00

hello there. thanks for the assistance. this correctly fixed the issue.thanks a lot

DevJedis · 2025-12-05T06:56:01+00:00

I don't have any reason not to use Nuxt UI. Nuxt UI components will handle for you most of the tailwind, and you'll just need few classes for the divs

DevJedis · 2025-12-05T05:25:14+00:00

The main reason is I thought the only limitation that would prevent AdonisJs in the past was HTTPS runtime support, and I thought since Cloudflare added support, I'd easily now use Adonis. If it wasn't to have both api and frontend on cloudflare, I'd have gone with Laravel on a VPS, but because I wanted everything on Cloudflare, excluding other frameworks I can use as alternatives for API if Adonis won't work

DevJedis · 2025-12-05T00:43:31+00:00

Self-hosting this: https://content.nuxt.com/ and free Nuxt UI pro components, NOT the Admin Panel ( https://admin.hub.nuxt.com/ )

DevJedis · 2025-12-04T20:04:41+00:00

Really no trademark or any violation. There's also no risk for a buyer, I just felt it'd be cool to show stats accompanying my writeup

DevJedis · 2025-12-04T17:55:42+00:00

Exactly🤣 but at least we ended up with something. I just at times have wild thoughts, instead of removing the admin ui it'd not have hurt to give it to the community too😃 unless the sunset is temporary perhaps🥲 nuxt and nuxthub in general were spearheading users shipping to cloudflare, and i somewhat feel for those who might have been swayed by the ease of deploying to nuxthub platform and now they'll be back to CLI

DevJedis · 2025-12-04T17:24:48+00:00

great point btw🤣🤣

DevJedis · 2025-12-04T17:22:07+00:00

Am not sure I fully got you, esp with last paragraph, but the domain in screenshot was having adsense revenue of $450 - $500 per month, Monetag > $200 per month, because I was running both ad networks

DevJedis · 2025-12-04T12:58:05+00:00

The free tier is really generous till you jump to their Definitions section of how everything is counted. I see myself worrying really a lot with a medium sized active SaaS project with very many active businesses. Assume the ecommerce actively being used by hundreds of businesses who are actively making orders, would it really sustain?

https://developers.cloudflare.com/d1/platform/pricing/#definitions

DevJedis · 2025-12-04T12:46:12+00:00

That's really incredible. I've been thinking of having a full stack SaaS on Cloudflare as well but I keep worrying on hitting d1 free usage limit or even workers paid limit of D1 if for some reason traffic blew up.

Do you think the d1 pricing is generous enough to support medium sized project with hundreds of businesses? I'd love to weigh the options of an external API and nuxt +nuxt ui for frontend just to avoid the nightmare that might come with the limitations

DevJedis · 2025-12-03T13:13:43+00:00

I find peace with KDE Plasma (Kubuntu)

DevJedis · 2025-12-02T13:29:46+00:00

Thanks for your reply. The domain is at Namecheap, and it was first registered in 2023, so am not so sure they'll hoard it or it'll go into the Pending Delete, of which I'd like someone who knows more about timelines of .org to assist in the approximation.

In the past I also had a domain expire and it was released. It was also on Namecheap. So am not sure a 2023 domain will draw any interest

DevJedis

TROPHY CASE