Ponzu – An open-source HTTP server framework and CMS in Go
1–10 of 43 posts
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#2Looks interesting, it would be nice if the ”Why?“ section contained comparisons to other CMSs.
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#3> Automatic & Free SSL/TLS
A couple of years ago, I wouldn't have believed we would be seeing essentially zeroconf TLS/PKI in software anytime soon. Letsencrypt, the "encrypt everything" movement, and people like Steve, Ponzu's author, have improved internet security tremendously at a time when it is critically needed.
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#4Does look pretty slick, but I imagine the flat nature of the content items will be limiting. In the example, song has an artist. But artist is a string vs a related content item.
I can't tell if that's an MVP type decision and will change later, or a design decision that won't change in the future.
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#5Boltdb sounds neat, but I swear no off-the-shelf tooling supports it.
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#6looks interesting
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#7Does look pretty slick, but I imagine the flat nature of the content items will be limiting. In the example, song has an artist. But artist is a string vs a related content item. I can't tell if that's an MVP type decision and will change later, or a design decision that won't change in the future.
Is it flat like wikipedia or flat like S3?
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#8Couldn't see any authentication system in Readme, Is there any auth mechanism that can be used for API usage?
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#9Kudos to the creators for getting the CMS field definitions right by allowing arbitrary amounts and types of fields!
It's so annoying to me that so many CMS's and static site generators start out with the assumption of 1 big rich text / markdown "body" for content and treat everything else on the page as miscellaneous stuff (meta-fields, yaml front-matter, etc).
Re: Ponzu – An open-source HTTP server framework and CMS in Go
#10Does look pretty slick, but I imagine the flat nature of the content items will be limiting. In the example, song has an artist. But artist is a string vs a related content item. I can't tell if that's an MVP type decision and will change later, or a design decision that won't change in the future.
Is it flat like wikipedia or flat like S3?
Not sure. I don't see any support for item relationships. It could just be a lack of documentation though.