dennisklappe/emdash-plugin-github-backup — explained in plain English
Analysis updated 2026-05-18
Keep a version history of CMS content edits stored outside of git.
Recover a deleted piece of content from a past commit.
Audit who changed which piece of content and when.
| dennisklappe/emdash-plugin-github-backup | 0xkinno/neuralvault | 0xmayurrr/ai-contractauditor | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 2/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a GitHub token with write access to the target backup repository.
This project is a plugin for emdash, a content management system that stores its content in a database rather than in git. Normally that means edits made by an editor never show up as file history anywhere. This plugin closes that gap by copying every content change into a GitHub repository, so the repository's commit history becomes a record of who changed what and when. Whenever a piece of content is created or updated, the plugin writes a JSON file for that entry into a folder in your chosen GitHub repo and commits it. It is smart about not creating duplicate commits: emdash sometimes fires its save event twice for a single edit (once for a draft, once for publishing), so the plugin compares the new content against the last backup and skips the commit if nothing meaningful actually changed. When content is deleted, the corresponding file is removed from the repo, though the old version stays recoverable through git history. If the plugin cannot figure out which file to delete, it writes a small placeholder file instead so the deletion is still logged. Commits are attributed carefully: by default they are credited to a neutral, no reply GitHub account rather than whichever person's access token was used, which avoids a confusing phantom user showing up in your commit list. When the plugin can identify the actual editor from the content's assigned author field, it will credit that person as the commit author instead. Setup involves installing the package, adding it to your emdash configuration with a target GitHub owner and repo name, and supplying a GitHub token with write access to that repository, either through settings, environment variables, or plugin options. If the token or repo details are missing, backups are simply skipped and your content save still goes through normally, so a backup problem never blocks an editor from saving work. It also attempts to copy any media files referenced in your content, though this only works when certain conditions are met. This is an independent, unofficial plugin, not built or endorsed by the emdash project itself.
Automatically backs up emdash CMS content edits to a GitHub repo as commits, turning database changes into a versioned git history.
Mainly TypeScript. The stack also includes TypeScript, GitHub API, emdash CMS.
No license information was stated in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.