Importing is still on the todo list and is being looked at, but that does not help you now. I think you are right in that some sort of banner and editing the text about moving between installation, can help prevent people from getting in your situation.
Reinier > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] [mailto:tracks- > [EMAIL PROTECTED] Namens Oliver Uvman > Verzonden: dinsdag 10 juni 2008 19:24 > Aan: [email protected] > Onderwerp: [Tracks-discuss] Help restoring from YAML-backup > > Hello! > > Imagine my huge surprise, despair, and drop in productivity when, > after a harddrive crash, I noticed that Tracks is incapable of > importing YAML-files! Maybe you should consider putting a huge > IMPORTING IS NOT YET IMPLEMENTED text on the Export page until > importing is implemented? Or at least a smaller warning text for > people intending to use YAML as backup. At least remove the text about > how YAML is good for moving data between installations? Something! > > But I'm not here to rant. The only thing that got lost during the > crash was MySQL and it's database. The other parts of Tracks work so > it will probably be easiest for me to change the install to use > SQLite, and in some way put the stuff in the YAML-file in there. A > friend I talked with this about said that something can be done with > Ruby? I don't know a bit of Ruby, though, so I would appreciate any > help I can get. Is it possible to save my Tracks data without manually > going through the 6600 line YAML-file? > > Regards, > Oliver Uvman > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
