5 ms·
YABT popped up shortly after ticgit -- same type of thing. Scratched and itch to try something, then let it fall off. I'm going to revisit it and see where it
by tswicegood 16y ago
YABT popped up shortly after ticgit -- same type of thing. Scratched and itch to try something, then let it fall off. I'm going to revisit it and see where it stands though. I'd love to get it to where it serves as the backend for GitHub Issues.
One of the reasons I wrote it instead of extending ticgit was that I wanted something entirely independent of any VCS. All stuff I need to get in a readme, though. :-)
- technoweenie 16y agoI worked on ticgit a little too. It's such a neat idea, but I'm not sure how it would work in practice. I think git repos would be best for syncing, but not the main data store on GitHub. I'm curious about using CouchDB, actually. It has similar versioning and replication features to git.
- fortes 16y agoHave you looked at ditz? http://ditz.rubyforge.org/ http://ditz.rubyforge.org/
- technoweenie 16y agoYup, I tried using it and ticgit for a little while. Didn't really care for either of them.
- tswicegood 16y agoYup - I tried a half dozen while thinking about starting YABT. None of them seemed to fit the bill just right.
- tswicegood 16y agoIf the storage API inside the project is good enough (something YABT's isn't yet), swapping out where it gets the data is a minor issue. You could use Git for the main storage, then have a web frontend that reads from Couch/Mongo/Redis/NewHotnessNotYetDiscovered and lazy loads from disk. A post-receive hook or two for expiring data in that cache and you're set.