Cloudflare Flagship
developers.cloudflare.com
Cloudflare Flagship
1–10 of 189 posts
Re: Cloudflare Flagship
#2Re: Cloudflare Flagship
#3Re: Cloudflare Flagship
#4 Q.Data.variant()
https://github.com/Qbix/Q.js/blob/main/src/js/Q.minimal.js#L...And on the back end, you'd use it like this:
https://github.com/Qbix/Platform/blob/main/platform/classes/...
Essentially, this can support a huge number of "variants" and within each variant you can have N equal segments. That will help you do A/B testing and flipping features on or off.
Re: Cloudflare Flagship
#5Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Re: Cloudflare Flagship
#6Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Re: Cloudflare Flagship
#7Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Re: Cloudflare Flagship
#8Worth noticing a Vercel equivalent: https://github.com/vercel/flags
Re: Cloudflare Flagship
#9Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Just let everyone have access to prod?
Re: Cloudflare Flagship
#10Cloudflare are winning these days, they’re just lacking good fine grained permissions. You still have to make an entirely separate account for prod, which messes up SSO since one domain can only be bound to one account.
Just let everyone have access to prod?