I built Opensource.builders using GitHub Issues as a CMS. Building 2.0 using an actual CMS though.
GitHub issues are not git and don't even use git.
Whoops, thought it said GitHub in the title
Ask HN: Apps that are built with Git as the back end?
11–20 of 68 posts
Re: Ask HN: Apps that are built with Git as the back end?
#12I have the same question, I am have a git based static generated blog, I am looking for something like
1. A git based tool to scrobble the music I am listening to, like Last.FM.
2. A status logger, I really, really miss the old MSN or GTalk days when there's a status line to show what my friends are doing or their mood. In fact most people have forgotten that's the original case for twitter.
3. A git based comment system to replace Disqus, I can merge for incoming comments or reject spam.
4. life streaming to log the movie I've watched or books I've read.
Re: Ask HN: Apps that are built with Git as the back end?
#13I think Delicious Library was for a while at least. I remember the author of it, doing a presentation about using git as storage:
https://academy.realm.io/posts/altconf-wil-shipley-git-docum...
Re: Ask HN: Apps that are built with Git as the back end?
#14Dataform comes to mind (if you set it up to use git like that)
Re: Ask HN: Apps that are built with Git as the back end?
#15WikiJS has a Git storage backend.
Re: Ask HN: Apps that are built with Git as the back end?
#16Very interesting! I had a look at your "RFC 001: Core Architecture" but one question remains. You mentioned "git as the backend". As far as I understand, you don't use the word "backend" in the classic frontend backend sense. Instead, you mean that Git is being used as a software repository and as a content database. Is that correct or am I missing something?
I'm already sold on the idea of using Git as a database for content and localization. But I'm obviously biased as we are working on a similar solutation ;) It is called FrontAid and it is a CMS that stores your (localized) content in a JSON file within your own repo. More information can be found at https://frontaid.io/
Using Git for content has some great benefits. Like complete version history, easy reverts (for devs at least), (feature) branch support, Git hooks, ... And of course, you own your content at all times.
PS: Both the "Editor" and "VS-Code-Extension" links in your repo are broken.
Re: Ask HN: Apps that are built with Git as the back end?
#17The Office 365 backend uses git to store snapshots of documents. [1]
https://github.com/microsoft/FluidFramework/tree/main/server...
Re: Ask HN: Apps that are built with Git as the back end?
#18The leading package manager for macOS Homebrew (https://brew.sh) is Git-based.
Re: Ask HN: Apps that are built with Git as the back end?
#19I'm using a webscraper that extracts data from some APIs, and stores all the data in a git repo periodically. Then you can see the data changing with tools like git and tig.
I love that pattern. I call it "git scraping" and I've been writing about it for a few years (and building tools too): https://simonwillison.net/series/git-scraping/
Re: Ask HN: Apps that are built with Git as the back end?
#20Very interesting! I had a look at your "RFC 001: Core Architecture" but one question remains. You mentioned "git as the backend". As far as I understand, you don't use the word "backend" in the classic frontend backend sense. Instead, you mean that Git is being used as a software repository and as a content database. Is that correct or am I missing something? I'm already sold on the idea of using Git as a database fo…
Maintainer of inlang here:
Correct, the term git backend refers to git as a content database (with built-in version control and automation).
Regarding front aid, great to see fellow startups working on solution built on git. It took months to realize the benefits of git and the logical step to build the backend on git. sorry, use git as the content database.
PS ty, fixed the links! :)