Re: [fluid-dev] Migration of services

[Elimar Green]

Just an update.  Using sqlite I was able to easily dump the tickets data.  I'll be looking into something like what Jimmy suggested to automate the submission of tickets.  Maybe I can do the same for comments too, though all the comments would be under one user, though I could indicate who the original user was in the comment.

Elimar

On Thu, May 20, 2010 at 10:25 AM, Elimar Green <address@hidden> wrote:

Thank you all for the responses and hosting offers!  Things are rolling along with the SourceForge migration path and their technical support has been very quick to resolve issues as they have come up.  I'm beginning to also think that the SourceForge path is best, so lets go that route.

https://sourceforge.net/apps/trac/fluidsynth/wiki

The FluidSynth SVN history is imported and accessible via Trac and the Wiki has been restored.  I have not yet added the tickets yet.  I will do this, since I'd like to try and keep the same ticket numbers so that Wiki references match.  Though this may prove to be too much of a pain.

The Trac database backup that I have is SQLite.  Thanks for reminding me about email addresses and passwords.  I don't think I'll be distributing it for that reason.  Would be nice if I could at least dump the tickets to some sort of accessible format though.  Any ideas on how to do this with Trac would be most helpful.

Best regards,

Elimar

On Wed, May 19, 2010 at 1:24 PM, David Henningsson <address@hidden> wrote:

On 2010-05-18 08:19, Elimar Green wrote:
> Any thoughts?  I think these are the options:
> - Find another place to host the original FluidSynth Trac install (any
> offers?)
> - Host SVN on the Trac host
> - Host SVN on Savannah or SourceForge and periodically sync it to the Trac
> host
> - Host Trac on SourceForge and manually re-create tickets, losing much
> history info, Ticket CCs, time consuming to re-enter data, etc.

I believe SF.net is the best option so far, and that it would be good to
have things settled in one place instead of having things scattered over
several places. Pedro's ideas about some kind of ticket text dump would
work, I guess.

> I'm completely willing to hand over the FluidSynth Trac tarball and SVN
> dump, to anyone who has more enthusiasm for setting this up somewhere.

I would very much like to have such a tarball and SVN dump, at least for
backup purposes. Does it contain sensitive information? E-mail addresses
I assume, are passwords properly salted or in clear-text? I'm thinking
other users might want to keep such things as secret as possible.

> I don't really have a lot of time or interest currently.

It happens that a person's priorities in life change. And that's okay.

// David

_______________________________________________
fluid-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/fluid-dev