[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tortoisesvn-users
Subject:    Re: Exporting variants to 3 different servers
From:       Stefan Hett <stefan () egosoft ! com>
Date:       2016-06-02 10:55:20
Message-ID: ad9fc298-4429-532c-00ab-7620c1a4a00d () egosoft ! com
[Download RAW message or body]

Hi Eric,
On 6/1/2016 10:53 PM, E. Mommsen wrote:
>
> Hi
>
> I am developing a piece of php/js-software for 3 different servers 
> which have a number of server-specific files.
>
> I am running Tortoise-svn to svn 1 working copy and up to now I am 
> handling the server-specific files manally.
>
> That's what I want to change now. How would I do that to simplify my 
> life in case of exports to the productive server systems?
>
Quite a lot of different ways to achieve that. One possibility:
Have three different projects in the repository. One for each server 
environment. In each project define an external to the common 
php/js-software.

Then the development of the php/js-software would go into the single 
php/js-software project and the checkout on the servers would go from 
the server-specific projects then.

An alternative would be to have different projects and merge them 
(presumably with some auto-merge script --- maybe via post-commit hooks).

-- 
Regards,
Stefan Hett

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3174083

To unsubscribe from this discussion, e-mail: [users-unsubscribe@tortoisesvn.tigris.org].
[Attachment #3 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Eric,<br>
      On 6/1/2016 10:53 PM, E. Mommsen wrote:<br>
    </div>
    <blockquote cite="mid:e2f64a84-ae9a-2ad8-cc34-04bc4b4e8bc3@arcor.de"
      type="cite">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div id="smartTemplate4-template">
        <div style="font-family: Arial,Helvetica,Geneva,Sans-serif;
          font-size: 12pt; text-align: left;">
          <p>Hi</p>
          <p>I am developing a piece of php/js-software for 3 different
            servers which have a number of server-specific files.</p>
          <p>I am running Tortoise-svn to svn 1 working copy and up to
            now I am handling the server-specific files manally. <br>
          </p>
          <p>That's what I want to change now. How would I do that to
            simplify my life in case of exports to the productive server
            systems?<br>
          </p>
        </div>
      </div>
    </blockquote>
    Quite a lot of different ways to achieve that. One possibility:<br>
    Have three different projects in the repository. One for each server
    environment. In each project define an external to the common
    php/js-software.<br>
    <br>
    Then the development of the php/js-software would go into the single
    php/js-software project and the checkout on the servers would go
    from the server-specific projects then.<br>
    <br>
    An alternative would be to have different projects and merge them
    (presumably with some auto-merge script --- maybe via post-commit
    hooks).<br>
    <pre class="moz-signature" cols="72">-- 
Regards,
Stefan Hett</pre>
  </body>
</html>


[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic