Noah Kantrowitz wrote:
> How about we just wait the 2 hours for an admin to notice and kick
> apache in the head?

2 hours long gone.

> I think this is being seriously over-thought. If people need the code
> for plugins, it should all be available on PyPI as a "mirror" (assuming

What's PyPI?
/L

> the author was wise enough to push copies there).
> 
> --Noah
> 
> Axton wrote:
>> On Nov 6, 2007 11:13 AM, Lars Stavholm <[EMAIL PROTECTED]> wrote:
>>   
>>> Axton wrote:
>>>     
>>>> On Nov 6, 2007 10:53 AM, Emmanuel Blot <[EMAIL PROTECTED]> wrote:
>>>>       
>>>>>> SVN 1.4+ has svnsync available which is also an option. It can be set up
>>>>>> to run as a commit hook and push out/sync changesets to a list of mirror
>>>>>> repositories or just be scheduled for periodic sync.
>>>>>>           
>>>>> Sure but this means TH needs to push information - therefore an
>>>>> operation is required on TH when a new mirror appears or needs to be
>>>>> removed.
>>>>>
>>>>>         
>>>> For mirrors, what about creating a daily copy of the repo using
>>>> 'svnadmin dump', then posting the file for public download.  Sites
>>>> that wanted to mirror could then fetch a copy on an interval and load
>>>> it using 'svnadmin load'.
>>>>
>>>> To ensure service, it could be worked out that in the event of a
>>>> failure at trac-hacks, a repository could be designated as a backup
>>>> working site.  The backup site could be kept up to date using svnsync
>>>> using a post-commit hook.  Changes on this site could be loaded to
>>>> trac-hacks when service is restored.
>>>>       
>>> That's all good ideas.
>>> How about mirroring the Trac site itself?
>>> /L
>>>
>>>     
>> How about the same arrangement so far as the schedule; just tgz the
>> resulting directory structure from trac-admin hotcopy.
>>
>> I have a hosted machine I can offer as a mirror if the owner of TH
>> will work with me to make some type of arrangement.  Host has 500gb
>> monthly transfer, runs Trac 0.10.3.1, svn 1.4.2, apache 2.2.4, python
>> 2.4, sqlite 3.3.10, linux x86.
>>
>> The authentication will be a little tricky, as my site may not be
>> configured like the TH site.  I use digest auth via TracAccountManager
>> 0.1.3dev-r1844.  The same set of htdigest credentials are used to
>> manage svn commit access.
>>
>> Axton Grams
>>
>> >>
>>
>>   
> 
> 



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to