Need help with flashbake?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

cmdln
447 Stars 38 Forks GNU General Public License v3.0 320 Commits 6 Opened issues

Description

Scripts to gather information for including in version history comments and to make using source control a bit simpler for non-technical projects.

Services available

!
?

Need anything else?

Contributors list

# 319,397
C
Shell
C++
182 commits
# 366,716
MATLAB
Shell
Rails
gtd
24 commits
# 480,011
PHP
HTML
Shell
17 commits
# 28,801
absinth...
Elixir
node
subcomm...
4 commits
# 328,859
Shell
C
webdriv...
seleniu...
2 commits
# 23,224
Nim
video-d...
Courser...
sqlite3
2 commits
# 728,252
Python
1 commit

Welcome to Flashbake

Flashbake is about helping writers use Git version control to archive the evolution of their work. This can include the initial creation of the work, edits to the work, as well as metadata surrounding the writing process.

The metadata is configurable and pulls in information from the user's lifelog such as recent social media posts, blog posts, music listening, current weather, location, and more. It then commits that metadata and textual changes to an archive at set intervals.

As Cory Doctorow describes it Flashbake is about recording, "Where am I, what’s it like there, and what am I thinking about?”

How Flashbake was born

Flashbake first rolled out in 2009 as a result of discussions between Cory Doctorow and Thomas Gideon. Cory was looking for a way to reintroduce the trail of edits, notes, annotations, and so on that grow out of writing by hand or typewriter; this collection of material automatically records how a piece of writing develops and can be a boon to historians, archivists, as well as the writers themselves.

With computers that natural archive disappears since writers are often using a single file or set of files that are constantly being edited. Version histories built into most text editing programs aren't up to solving this problem, nor are automated backup services.

Source control, however, is an excellent tool for archiving incremental changes, but most tools expect the author to manually commit their changes along the way. Flashbake takes these two notions and combines the convenience of automated backup with the power of source version control.

How to use Flashbake

If you'd like to install Flashbake and use it for your projects check out the wiki for instructions on how to install, configure, and run Flashbake.

Joining the Flashbake community

If you'd like to contribute to Flashbake by helping with code or documentation, check out our contributor's guide.

Further reading

Cory Doctorow's initial blog post about the inspiration for Flashbake.

Thomas Gideon's initial blog post about developing Flashbake.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.