What does articy:draft use Subversion or Perforce for? MULTI-USER

Each articy:draft partition is represented by a file in the Subversion repository or Perforce depot. articy:draft manages these files "under the hood". Each time the user updates/claims/unclaims a partition, articy:draft internally sends commands like Check out, Check in, Get lock, Commit, Update to Suberversion/Perforce.

This gives you the advantage of having your precious project data stored in a secure, revertable and backupable storage.

In addition to that, change lists are generated for all actions the user performs. articy:draft can write those changes as custom commit messages into the repository/depot and view them in the change history of every partition.

Available repositories

articy:draft lets you choose between three different kind of repositories/depots for your multi-user project:

• Internal Articy Subversion
• Subversion (SVN) 1.6/1.7
• Perforce provider

Using Internal Articy Subversion

If you don't have an already existing Subversion or Perforce server up and running, the first choice might be the most suitable for you. articy:draft comes with an integrated Subversion server. This means you don't have to bother about repositories at all. Just choose a repository-path in the "source control" page of the new/import project assitant and you're all done.

Using Perforce

If you don't have Perforce at your studio but consider using it, you can start with the Trial version.

Host (and port number)

The host describes the address under which Perforce can be reached.

If you want to access a Perforce-based articy:draft project from outside your LAN you need to make sure, this host address and port number are also accessible from outside.

Depot name/path

Please fill in the depot name/path into this field. You can easily copy it from your Perforce client.

Using Subversion (SVN) 1.6/1.7

Repository-URL (internal)

Use this field to specify the base URL used to access the repository server from within the network.

Supported schemas are:

• "svn:" - The URL to be entered starts with "svn:", then comes server name and - optionally - the port number. For example: svn://subversion:3691
• "http:" / "https:" - When using http(s) based access (e.g. with VisualSVN) the URL has the following format: http(s)://server-name[:port]/mountpoint/repository-name, where:
  
  • mountpoint specifies the folder the webserver has mounted the SVN service
  • repository-name specifies the repository to be used
  For example: https://subversion:8443/svn/articydraft
  

Repository path

Here you have to set the project's base path within the SVN repository, starting with a "/".
For example: /MyProjectName

Repository-URL (external)

In a scenario when team-members work from a home office and don't use a VPN connection to connect to your company, this setting is required. Otherwise just leave it empty.
The format of the URL expected here is the same as for the 'Repository-URL (internal)' (see above), but you can set a completely different access path, like svn://mycompany.dyndns.org:5005 or https://mycompany.dyndns.org:7284/svn/articydraft.

articy:draft automatically selects the best usable Repository-URL when needed (creation, import or opening of projects).