On 5/22/22 14:40, Nico Kadel-Garcia wrote:
Why would you want to move a Subversion server to a Windows system?
Because that is what poster said they were migrating from. In existing
deployments keeping the current authentication, logging and
administration experience is probably more importa
Den sön 22 maj 2022 kl 14:41 skrev Nico Kadel-Garcia :
> On Sun, May 22, 2022 at 4:24 AM Andreas Stieger
> wrote:
> >
> > Hi,
> >
> > On 5/18/22 16:54, Mark Phippard wrote:
> > > If you can use the same DNS hostname for the new server there will be
> > > no impact on your clients
> >
> >
> > Exce
Den sön 22 maj 2022 kl 17:59 skrev Bo Berglund :
[...]
> So the relevant question for him is what kind of server they are running...
> If it is VisualSVN then they should go to that maintainer and ask for help.
>
>
> >There are real performance tuning issues for either httpd or svn+ssh
> >based ac
On Sun, May 22, 2022 at 12:02 PM Andreas Stieger wrote:
>
>
> On 5/22/22 14:40, Nico Kadel-Garcia wrote:
> > Why would you want to move a Subversion server to a Windows system?
>
>
> Because that is what poster said they were migrating from. In existing
> deployments keeping the current authentica
Hi,
> If you have not used any of the advanced features in VisualSVN [...]
FWIF... The free VistualSVN version can* be set up to do full write-through
proxying and async replication. It ships all the modules. (* last confirmed in
~2015)
Andreas
In my case, I have no choice in the matter of what server and OS to move to. We
don't use VisualSVN. We just use Tortoise with Subversion. When we last did a
migration from one Windows server to another, it was a tedious process of
contacting the users of the repository, asking them if the repo
On Mon, May 23, 2022 at 6:16 AM Morin, Michael wrote:
>
> In my case, I have no choice in the matter of what server and OS to move to.
> We don’t use VisualSVN. We just use Tortoise with Subversion. When we last
> did a migration from one Windows server to another, it was a tedious process
> of
: Re: Moving the entire SVN instance to a newer Windows server
EXTERNAL: This email originated from outside of the State of Maine Mail System.
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Mon, May 23, 2022 at 6:16 AM Morin, Michael
Hi,
> We just use Tortoise with Subversion.
You mean just plain file:// access? (no mod_dav_svn or svn)? Then there is not
even a Subversion server involved. Is there any way you can re-use the hostname?
Andreas
On Mon, 23 May 2022 11:03:32 +, "Morin, Michael"
wrote:
>>On Mon, May 23, 2022 at 6:16 AM Morin, Michael
>>wrote:
>>>
>>> In my case, I have no choice in the matter of what server and OS to move
>>> to. We dont use VisualSVN.
>>>We just use Tortoise with Subversion. When we last >did a m
-Original Message-
From: Bo Berglund
Sent: Monday, May 23, 2022 8:09 AM
To: users@subversion.apache.org
Subject: Re: Moving the entire SVN instance to a newer Windows server
EXTERNAL: This email originated from outside of the State of Maine Mail System.
Do not click links or open
On Wed, May 18, 2022 at 9:46 AM Morin, Michael wrote:
>
> We need to move Subversion off of a Windows 2012 server and onto a Windows
> 2019 server. Is there a simpler way to do this other than moving each
> repository one by one? I have over 170 repositories that I need to migrate to
> the new
Hi,
On 5/18/22 16:54, Mark Phippard wrote:
If you can use the same DNS hostname for the new server there will be
no impact on your clients
Except for possibly a change server-side certificate which may have
changed (and not properly verified before). Can be addressed with
testing, and it help
On Sun, May 22, 2022 at 4:24 AM Andreas Stieger wrote:
>
> Hi,
>
> On 5/18/22 16:54, Mark Phippard wrote:
> > If you can use the same DNS hostname for the new server there will be
> > no impact on your clients
>
>
> Except for possibly a change server-side certificate which may have
> changed (and
On Sun, 22 May 2022 08:40:55 -0400, Nico Kadel-Garcia wrote:
>On Sun, May 22, 2022 at 4:24 AM Andreas Stieger wrote:
>>
>> Hi,
>>
>> On 5/18/22 16:54, Mark Phippard wrote:
>> > If you can use the same DNS hostname for the new server there will be
>> > no impact on your clients
>>
>>
>> Except fo
15 matches
Mail list logo