Jonas Borgström kirjoitti: > Jani Tiainen wrote: >> Emmanuel Blot kirjoitti: >>>> What would be best option to make transfer? Setup projects as blank in >>>> Linux and copy only DB? Or copy whole projects and update paths >>>> accordingly? >>> Well, the safest way is to use portable file format between two >>> different hosts (if the HW architecture is different, you might get >>> real issues if you simply copy binary files) >>> >>> Use 'sqlite3' to dump and re-read <project>/db/trac.db files, and >>> svnadmin for the Subversion repositories. >>> Other files can be copied as is, although I would recommend you run >>> 'dos2unix' or the eq. command on <project>/conf/trac.ini files to >>> convert CRLF end-of-lines into LF end-of-lines. >>> > > Sqlite dump/load should only be necessary when moving from sqlite2 to > sqlite3. The sqlite file format is platform independent. > >> Well I meant "dumping" in some protable format. >> >> But still, would anything bad happen if I recreate my trac projects and >> just replace db with dump data? > > Simply copying the env to the new system should work. One possible issue > might be file attachments when an environment is moved from a case > insensitive filesystem to a case sensitive filesystem. But iirc NTFS is > case preserving so this might not be an issue after all...
Yep, NTFS is (by default, can be changed) case insensitive, case preserving. So I'm pretty much good to go. Altough still bothers me: is it better to setup projects before copying data (creating new ini files etc?) or doesn't matter? -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
