Version 0.1, open source under Apache 2.0

Ship new seed data without undoing your customers' edits

Roles, permissions, plan tiers, workflow states: the rows your app ships with change every release, and admins change them too. Bootstrapping merges the two, value by value, keeps every local edit, and stops to ask when both sides changed the same thing.

How it works Quick start
The editor role as last applied, as the new seed has it and as the admin left it. The description changed only in the seed and is updated. The name changed only locally and is kept. Had both changed, differently, the apply would stop and ask.

492,228

Values checked across 1,200 random histories of seed versions and admin edits, none overwritten without a conflict

400

Applies killed with SIGKILL, every database found exactly as before or exactly as after

1 of 8

Processes applying the same seed to one file at once that write, in each of 60 rounds

129,632

Checks that values compare the way SQLite stores them, across 16 column types

Measured on Linux x86-64 with 2 CPUs. Every number comes from the test results in the repository.

Articles

the name

Why the Project Is Called Bootstrapping

To bootstrap a computer is to take it from nothing to running: a tiny first program loads a bigger one, which loads the system. The word comes from the old joke about …

Shipping reference data to customers' databases?

If your application ships roles, permissions, plans or other seed data that customers then edit, the project would like to hear how you upgrade it today and where it hurts.

Contact