Search code examples
network-programmingperforcenasp4v

P4D and P4V configuration...Depot and workspace directories

Current p4 is configured as shown in screen capture I attatched. I've set p4d up in our NAS (Synology DS416play) and made repository directory there.

I'm trying to use P4V in workstations while NAS does p4d stuff and handle depot.

Seems I've set identical machine for both client and server. This I thought might be my issue directly associated with my question.

Q) Can I put depot in server (our NAS) and workspace in linked computers? I believed that's how it should've worked, but I'm getting something wrong. I've tried to handle this task mostly in P4V, but there I could only make changes of directories where both Depot and Workspaces are same route. Can you give a right direction how I should really do my configuration as I wished?

Solution

  • P4V is not used to configure the P4D server. The actions you were taking in P4V were only configuring your particular workstation's P4V setup.

    Perforce is a client-server system. You must configure the server software and run it on some server machine which is accessible by all your clients.

    On that server machine, the simplest configuration requires you to decide:

    1. Where should the server store its data files (P4ROOT)?
    2. What network address should the server accept connections at (P4PORT)?

    Then each user installs P4V on their workstation and configures their own workstation to access the server.

    The client configuration is straightforward, and generally consists of three settings:

    1. What's my username on the Perforce server (P4USER)?
    2. Where do I want my copies of Perforce-managed files to go on my workstation's filesystem (P4CLIENT)?
    3. What's the network address of the Perforce server (P4PORT)?

    You may also need to configure your networking software (firewalls, routers, etc.) so that Perforce's TCP/IP connections can be established on the P4PORT that you picked.

    And, naturally, be sure that you monitor your server: take regular backups (and ensure they are stored securely), make sure your server has adequate disk space, CPU, RAM resources, etc.

    There are many other configuration settings, both on client and on server, but these are the basics.

    EDITED TO ADD:

    On the server, there are two sets of data:

    1. The contents of the files that you have stored in Perforce (typically referred to as "the versioned files", or "the archives").
    2. A database with extensive metadata about the files, changelists, integrations, users, and other aspects of the Perforce SCM.

    (There are a few other sets of data, such as checkpoints, journals, logs, etc., but the above are the principal datasets.)

    The database is stored as a set of files with the naming pattern 'db.*' (db.user, db.rev, etc.) and are located in the P4ROOT directory.

    The archives default to being stored in the same location as the P4ROOT, but can be stored elsewhere. The location of the archives is configured on a depot-by-depot basis using the p4 depot command, as documented here. If you want to store your archives for a particular depot in some other location, check the instructions here and here.