Is there a Cloudflare solution which can compete with netlify

Developers Cloudflare Pages
1

Hi there,

I use the Decap CMS https://decapcms.org/docs/add-to-your-site/#authentication on netlify it is a very simple process using the netlify identity. This help me control who can access the CMS and edit the static site.

Is it possible to achieve the same on cloudflare when hosting website on cloudflare pages. The CMS is accessed by clients, so called SEO experts and content writers. is it is not limited to my access only. Is it possible to achieve this with cloudflare if yes how.

Thanks

4

Perhaps this article about using Netlify CMS (now Decap CMS) without Netlify might help

1 Like
5

Hi @anon9246926

I do not wish to use a 3rd party server such as glitch as otherwise I prefer Netlify.

What I want since the site is hosted on cloudflarepages is to know if cloudflare have a similar service which can connect with the githubgateway or GitHub backend so I can easily just add the Decap CMS to my static site. Without involving other 3rd party servers.

An exception for authentication for example https://auth0.com to handle user registration etc. I need to know if cloudflare services can compete with Netlify when it comes to static site hosting? and what solution it provide to add a CMS such as Decap to the static sites hosted on cloudflare.

Thanks

6

@anon9246926

Offtopic but just want to compliment your website, very cool and unique well done :clap:

7

I think this one is better https://puginarug.com/ :smiley:

1 Like
8

@anon9246926 Haha unfortunately we don’t see many unique concepts these days. useless but cool

Coming back to the main topic, do you know if your above solution can work within cloudflare for example using the workers or the Zero Trust solutions provided by cloudflare.

I host some websites on Netlify just for the identity feature but would like to move them to cloudflare due to affordability and free analytics etc.

thanks

9

Back on topic…

Netlify CMS (sorry, Decap CMS) uses Netlify Identity to handle login but writes content back to git. This is done regardless of the authorization mechanism (as far as I know.) It is possible to set the CMS up locally only without the need to authenticate (which I have done previously) and handle the git push yourself (this then enables building on any platform.)

As far as Cloudflare/Netlify competing, having used both (and still using both) they work differently. Some things one does better, some things the other.

A quick DDG search and I found GitHub - microfeed/microfeed: a lightweight cms self-hosted on cloudflare, for podcasts, blogs, photos, videos, documents, and curated urls., and there are other options too Cloudflare Pages now partners with your favorite CMS.

Also found GitHub - i40west/netlify-cms-cloudflare-pages: Oauth API to run Netlify CMS on Cloudflare Pages

2 Likes
10

@anon9246926

This seems too technical for me apart from this great solution you provided https://github.com/i40west/netlify-cms-cloudflare-pages but I wonder how come cloudflare does not have something equal to Netlify identity. where I can let users signup and login.

I hope they will bring something to cover this gap as I loved the whole pages experience but just because of this technical difficulty when hosting on cloudflare vs netlify is the reason I think I will just stay with netlify.

@cloudflare Pages are not yet ready for anything more than hosting a static site on dropbox :frowning:

11

Have you seen Access policies · Cloudflare Zero Trust docs? It provides scope (though I haven’t played with it that much) for user access (including sign-up), roles, and more, much like Netlify Identity does.

There is even a plugin for Cloudflare Pages Cloudflare Access · Cloudflare Pages docs

Cloudflare Pages is a lot newer product then Netlify is, so saying that it is lacking this that or the other isn’t entirely fair on the platform.

I don’t agree with this at all. The functions with Cloudflare Pages are, IMHO, much easier to work with than Netlify/AWS Lambda.

12

Thanks @anon9246926 for providing detailed info

However as a user I want to let @cloudflare know that their pages is ■■■■ comparing to netlify and instead of setting all this messy access it is much easier to use auth0 and host and manage websites on cloud server.

I hope in the near future you provide some solution for Decap CMS thanks

13

Spent a little time playing with Access today with the examples given in the Pages documentation. I honestly find it easier than Netlify Identity. I’ve tried auth0 in the past and found it painful.

Guess that’s why so many offerings exists: everyone has a different way of working just like the various services do.

2 Likes
14

Thanks @anon9246926 I will do, meanwhile if you write a post regarding the setup of decal cms on cloudflare pages please do ping me thanks a lot

1 Like
15

Hello,

I am facing the same issue and I understand that the best solution for now to completely using decap cms inside cloudflare pages is to use Pages Functions.

And GitHub - i40west/netlify-cms-cloudflare-pages: Oauth API to run Decap CMS (formerly Netlify CMS) on Cloudflare Pages provides the implementation.
Thanks @anon9246926 for pointing to this repo.
I am going to try this approach for my site.

So far so good.

However, I think Cloudflare could do better by supporting this kind of Pages Function natively?
So, for example, after configuring Cloudflare Access the write access to the GitHub repo, it will automatically handle the process similar to the Pages Functions in GitHub - i40west/netlify-cms-cloudflare-pages: Oauth API to run Decap CMS (formerly Netlify CMS) on Cloudflare Pages.

This will be a huge advantage for Cloudflare to be more competitive in the market, IMHO.

16

I understand that using Pages Function will have a quota for free tier.
It means user needs to consider both quotas of cloudflare access and Pages Function.

I wonder if Cloudflare could find a better way, that is implemented directly into cloudflare access instead of a built-in Pages Function. That’s would be a perfect solution then.