--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/e5c80c77-10f7-4230-b1fb-e7820c55ea5dn%40googlegroups.com.
Hi Michael,for migration it should be simply moving files from one machine to the other, ok i talk about stand alone trac but sqlite is a file and when your trac ini was working you just need to make sure the sqlite file is in the same path or adjust trac.iniat the end of the day migration to a new machine isnt more than that, well you might need to check plugins if you migrate to a other version of trac but migrating a project isnt more then copy filescheersMArkus
If they were running PostgreSQL or MySQL you will need to load the SQL. If SQLite, it's just a file like MArkus mentioned and not SQL load is needed.
You received this message because you are subscribed to a topic in the Google Groups "Trac Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/trac-users/GmajEM9Evj4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to trac-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CAJ4osOmUNwUXwcz7R7oe4UKE9rtXz5XvDgZ4i3maMpdv7FcM2Q%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Trac Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/trac-users/GmajEM9Evj4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to trac-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/4d88d35a-41de-478c-a15d-2baf7e394969o%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CACjZjXXnfNHVMjoP__7i_WoZCcsgh8aTvaEf7G%2BWex%2Bd8pcRMQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CAJ4osO%3DkcaHbVX2jzi6GHi7xYbPmsMSxQr1xiYtExPGT5G3LZQ%40mail.gmail.com.
Ok, I think I need to do more investigation.Cheers,Mike
Hi Ryan,I did start a stackoverflow question on this but managed to resolve that question myself and before stumbling on this mailing list.CloudForge was using Trac 0.12.5, new VM uses Trac 1.5.1, they provided the same sort of project folder structure so I assumed to copy across to the new project but got stuck on the database which I had to load using the sqlite3 command line.I'm pretty sure I copied across the full directory structure to the latest test project I have - the users have just not been migrated to the new VM.Thanks for your help.Michael
Hi Michael,please be aware that db access and trac access two different things! the db user is imply there to read and write to the db. Users in Trac authentication is handled by different methods like htdigest. so you need to figure out what method is used, for htdigest you usually have a file with the login informations (shouldnt be accessible from web!)hope this gets you a bit further, regarding the dump , i dont know if sqlite has a special "dump" or simple a backup of the db file.again db user and trac users are diffrent things!cheersMArkus
Hi guys,Just to update you I think I'm sorted now - I have manged to add the required users as suggested to the apache servers htpasswd file as required (thanks Markus for the -c info).I have added users as per the Trac installation and this works fine. I did spend some time looking into the AccountManager plugin but at the moment this is just a nice to have and not required.Thanks all for your help and patience.Just a bit off topic - why do you guys not use StackOverflow?Cheers,Mike