Hi I think the people who have the most problems getting their data out of Tracks en into another install of Tracks are those using a online provider, not their own install. So I think the per-user yaml export / import is most important.
Reinier > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] [mailto:tracks- > [EMAIL PROTECTED] Namens Geoffrey Donaldson > Verzonden: zaterdag 5 juli 2008 13:21 > Aan: [email protected] > Onderwerp: [Tracks-discuss] Yaml Importing > > Hi All, > > I've been talking to bsag about yaml importing. Recently I needed to > import some yaml data into a clean tracks install, so I wrote up some > code to do it. But this would only work if you wanted to start from an > empty database, or override existing data with what you have in your > yaml file (ie, restoring to a saved point). > > Bsag mentioned that the plan was to integrate yaml_db somehow. But the > down side to this is that it is used for dumping the whole database, a > useful feature, if you are the admin ... but for single user backups > (or in the case of a hosted version of tracks) this isn't really an > option > > So, my question to you is, where do you see the yaml export's going? > Should we make an interface for the users(well admins) to use yaml_db > to backup/ restore. Should we stick with the current, per user, > export, import. > > My feeling is that it might be worth having both options. > > What do you think? what are the benefits of these options? > > -- > Geoffrey Donaldson > > > _______________________________________________ > 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
