[Drawkit] File format extensions

Eric Jarvies 7 at ericJarvies.com
Fri May 16 04:35:17 PDT 2008


Graham,

On May 16, 2008, at 4:33 AM, Graham Cox wrote:

> Thanks for the comprehensive info Eric.
>
> This jibes with what I gleaned from the svn book. What I'm in the  
> dark about is this - if I run svnadmin on my local machine, what is  
> path?

please clarify what you mean by running svnadmin on your local  
machine.  do you mean you have subversion running on your  
localhost(local machine), and your original repo is on this same  
localhost(local machine), and you are using terminal commands to  
access this localhost repo?  if this is the case, then your path  
should be exactly what it is on your local machine(/path/to/dir), the  
same path that you use to check in/out your revisions of the  
respective/applicable repo.  once you've dumped it, then you can  
compress that file, or simply ftp as it is, to your new host.    
perhaps i have misunderstood your question?

svnadmin dump path/to/repo > dumped.repo

> I don't have anything but FTP and HTTP access to my host, as far as  
> I can see (not even ssh)

if you do not have terminal/shell/ssh access to your web hosting  
account, it means you will need to park your dumped.repo file into  
your ~/ root directory on your web hosting server for which you have  
ftp access.

then use the gui/front-end your host provides to create subversion  
repos, and go ahead and create a new repo[repository-name].  but do  
not check anything into it.

then make a request for your host tech support to complete the  
process.  ask them to take the dumped.repo file you made from your  
localhost svn, which you ftp'd to your web hosting account, and have  
them do the following using their terminal access:
svnadmin load repository-name < dumped.repo

then have them do one more thing:
svn switch --relocate oldurl newurl

this should do the trick.

however, i would strongly suggest moving to a web host like  
webfaction.com, as they provide terminal access so your svn and trac  
creations may easily be managed via terminal/ssh.  or even better,  
slicehost.net, as they provide virtual machines/slices(soft/hard  
reboot control, complete control over os install, and apt-get, etc.  
packages).  when the host does not provide you with terminal access,  
your hands are rather tied, unless of course their tech support  
handles such matters upon request.

regarding your localhost repo... you could easily setup a new/second  
repo on your localhost, and then dump your existing/first repo, and  
proceed to load it into the new/second empty repo, just to get your  
hands dirty, and make sure you do it right.  with subversion, you can  
easily create multiple repositories.

regards,

eric



> - it's just the usual sort of common-or-garden webhosting package  
> except that it supports svn repos. I have created the repo using the  
> web front-end that the ISP provides, and I have an http URL to it  
> for check in/check out, etc. That's fine for starting a new repo  
> from scratch but I just don't see how I am supposed to move an  
> existing repo to it. Using the URL path in svnadmin doesn't work.  
> That's my stumbling block! I am probably missing something obvious.
>
> Regarding a Trac front end - I suspect the answer may be no because  
> I'm not in a position to set up any old software on the host - only  
> those packages that the ISP provides and this isn't one of them.
>
>
> cheers, Graham
>
>
> On 16 May 2008, at 4:10 pm, Eric Jarvies wrote:
>
>> Graham,
>>
>> it should be fairly straight forward...
>>
>> dump existing repo:
>> svnadmin dump /path > draw_kit_repo.svn_dump
>> tar zcf draw_kit_repo.tgz draw_kit_repo.svn_dump
>> scp draw_kit_repo.tgz newhostname:/path
>>
>> create your new repo on new server/host:
>> cd /path/to/new
>> svnadmin create draw_kit_repo
>> tar zxf draw_kit_repo.tgz
>> svnadmin load draw_kit_repo < draw_kit_repo.svn_dump
>>
>> i would suggest you force subversion to use the same UUID for the  
>> new repo as the old repo, by adding --force-uuid to your svnadmin  
>> load command.  if you've already loaded the repo, you can set the  
>> UUID later, but it's better to do it from the get-go.
>>
>> the dump file will be a lot larger then the repo itself, as it  
>> contains all versions.  if you want to save on disk space, use the - 
>> deltas switch, thus making successive revisions of files output as  
>> compressed, binary differences, like file revisions are stored in  
>> the repo.
>>
>> can also do:
>> svnadmin dump [old_repo] | ssh-C [host] svnadmin load [new_repo]
>>
>> i trust there will not be anyone posting any revisions to your old  
>> repo during the time of your dump, but in case it does happen, you  
>> can of course import any new revisions from the old repo to the new  
>> repo by creating an incremental dump:
>> svnadmin load /path < rev123.svn_dump
>> and then import the above revision from the old server to the new  
>> one using:
>> svnadmin load /path < rev123.svn_dump
>>
>> if need-be, to save time, in the new repo, you can turn off the  
>> syncing feature(just for the import) to speed things up:
>> svnadmin create --fs-type bdb --bdb-txn-nosync repos
>> then do the import, then turn on syncing again by editing the repos/ 
>> db/DB_CONFIG file editing out the line:
>> set_flags DB_TXN_NOSYNC
>> then recover the repo:
>> svnadmin recover repos
>>
>> good luck!
>>
>> are you going to install a trac front-end for the new repo?
>>
>> regards,
>>
>> eric
>>
>>
>>
>>
>>
>>
>> On May 15, 2008, at 11:09 PM, Graham Cox wrote:
>>
>>> Hi Eric,
>>>
>>> Thanks for the offer! I actually have the repo all set up and  
>>> ready to go, so it's not the hosting that's the issue, it's  
>>> transferring from the current repo without losing the history. I  
>>> know I need to do a dump but it's not clear how one can do that  
>>> from a remote host.
>>>
>>> cheers, Graham
>>>
>>>
>>>
>>> On 16 May 2008, at 12:08 pm, Eric Jarvies wrote:
>>>
>>>> Graham,
>>>>
>>>> I would be willing to setup an svn/trac repo for DrawKit, and  
>>>> provide read/write access to the server(ssh/etc.).  drawkit.net  
>>>> domain is available, so that could be registered, and the repo  
>>>> could be given svn.drawkit.net / trac.drawkit.net(or whatever).
>>>>
>>>> Eric
>>>
>>> _______________________________________________
>>> Drawkit mailing list
>>> Drawkit at lists.apptree.net
>>> http://lists.apptree.net/listinfo.cgi/drawkit-apptree.net
>>
>> _______________________________________________
>> Drawkit mailing list
>> Drawkit at lists.apptree.net
>> http://lists.apptree.net/listinfo.cgi/drawkit-apptree.net
>
> _______________________________________________
> Drawkit mailing list
> Drawkit at lists.apptree.net
> http://lists.apptree.net/listinfo.cgi/drawkit-apptree.net



More information about the Drawkit mailing list