Live data from Hacker News

Show HN: Self-hosted CMS on serverless Cloudflare

github.com

11–20 of 94 posts

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#12

Why mix the type of software (A CMS for certain use cases) with the distribution mechanism (Cloudflare Pages etc)? Shouldn't that be two seperate issues?

My guess would be:

Traditional CMS you do the setup and plumbing in the server because you have full control

Static website hosting you prebuild a website and push it up all complied and done but in a standard supported format, do it easily can go to different providers.

There's not much in between, because you can't (easily) write code that is happy to run in two different systems controlled by other people with different plumbing under the hood... It's certainly doable, but the more you generalize the more complicated your code gets... and the less you can benefit from the vendor specific stuff (e.g. removing features that one side does not support ... Or adding code to use it if it's there -- which makes code even more complicated)...

Edit: and to the point of code complexity: if you did this all yourself in an alpha release, you likely would make a company/product like forestry (mentioned elsewhere in this discussion) because you've made something some people would consider somewhat or very valuable

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#16

Earlier quoted context omitted.

You host it on your own Cloudflare account.

Are you self-hosting your pictures when you upload photos to your Google Photos account?

Is this GitHub repo were looking at self hosted because it's his accounts repo?

I think you can ask 3 people this question and get 5 answers to where the "self hosting" line is drawn...

I am not sure were I would draw this line myself :-)

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#17

I just use PicoCMS and upload my markdown files through FTP. I don't think there's anything out there that can compete with the simplicity of this solution, not even static site generators. It uses templates with Twig, and it's very simple PHP so you can host it anywhere. I once hit the frontpage of a big aggregator from my country and it handled like it was nothing from a very cheap shared hosting. From my Linux Min…

is picocms still a static site? cms like drupal,wordpress can control content access with password,which is where cms stands out.

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#18

Earlier quoted context omitted.

You host it on your own Cloudflare account.

Are you self-hosting your pictures when you upload photos to your Google Photos account?

Self-hosting means the ability to host and run the code on your own server (home or webhost). Since Microfeed is built on the cloud services offered by Clouflare, you technically can't run it independently on your own server as you will still have to use the Clouflare services:

    microfeed uses Cloudflare Pages to host and run the code, R2 to host and serve media files, D1 to store metadata, and Zero Trust to provide logins to the admin dashboard. 
@jacooper is correct that the term has been wrongly used by the creator.

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#19

I just use PicoCMS and upload my markdown files through FTP. I don't think there's anything out there that can compete with the simplicity of this solution, not even static site generators. It uses templates with Twig, and it's very simple PHP so you can host it anywhere. I once hit the frontpage of a big aggregator from my country and it handled like it was nothing from a very cheap shared hosting. From my Linux Min…

There are different definitions of simple. I found wordpress simple because I could access the UI to post from any device. I could upload images, save drafts, and preview posts. My static site, basically requires a desktop/laptop PC and to preview I have to build the site. This is far less simple to use even if it's simpler to run

Re: Show HN: Self-hosted CMS on serverless Cloudflare

#20
I use middleman[^1] + bulmaCSS + FontAwesome but host on github using the `github.io` domain and upload podcasts to "archive.org"[^2]. I choose this setup to make sure content will survive as much as possible.

ps. You might want to consider a donation to the internet archive, see [^2] - no affiliation, just a happy user.

[^1]: https://middlemanapp.com/

[^2]: https://archive.org/

Post reply on HN