convore.json/groups/kynetx/commit-on-save-manual-commit/messages.json

[{"user_id": 30462, "stars": [], "topic_id": 45661, "date_created": 1316710635.634244, "message": "I'm looking at building a KRL ruleset filesystem that would make your rulesets look like local files. I could build it like the current 'krl' gem, where you work with a local copy and then 'commit' your changes. I could also make it live, so whenever you write to the files the changes go immediately to Kynetx. Either way you would still have a \"deploy\" command taht would deploy the 'current' version.", "group_id": 236, "id": 2189913}, {"user_id": 30462, "stars": [], "topic_id": 45661, "date_created": 1316710725.489608, "message": "Would you rather have it be 'commit on save' or do you prefer to manually commit (when you feel like it)? Any downside to 'commit on save'?", "group_id": 236, "id": 2189922}, {"user_id": 30494, "stars": [], "topic_id": 45661, "date_created": 1316783890.067925, "message": "I wouldn't save a ruleset and go away from my computer. I will always test it right after the saving so that when I work on it again I know I have something stable. In order to test my changes I need them to be commited so I would opt for \"commit on save\" .", "group_id": 236, "id": 2196359}, {"user_id": 30462, "stars": [], "topic_id": 45661, "date_created": 1316793060.14779, "message": "That brings up an interesting point. 'Commit on save' means I can run the whole thing in memory. Otherwise I have to make a local copy of any changes, something that will survive a reboot.", "group_id": 236, "id": 2197581}]