README.md #2

FSClient

This is a proof-of-concept "file system client" that uses Fuse for OS X to handle many of the "distracting" tasks of interacting with a Perforce server. It mirrors an existing Perforce client workspace on your system. As you add or edit files, we handle running p4 add or p4 edit in the background.

Requirements

  • OS X, I'm building for 10.10
  • osxfuse - see vendor/ directory, but this must be installed before using

Building

This project uses CMake.

Setup

  • Your client must have a .p4config file in it's root directory.
  • You should execute p4 login before using this client
  • Right now, this does not tweak read-only status. You probably want allwrite on your client.

Running

Typical runtime:

fsclient -w ACTUAL_WORKSPACE_DIR -m PATH_TO_MIRROR

Both locations must exist before running.

If you're done, make sure no app is referencing files in the mirror, then unmount it:

umount PATH_TO_MIRROR
# FSClient

This is a proof-of-concept "file system client" that uses [Fuse for OS X](https://osxfuse.github.io/) to handle many of the "distracting" tasks of interacting with a Perforce server.
It mirrors an existing Perforce client workspace on your system.
As you add or edit files, we handle running `p4 add` or `p4 edit` in the background.


## Requirements

* OS X, I'm building for 10.10
* osxfuse - see vendor/ directory, but this must be installed before using


## Building

This project uses [CMake](https://cmake.org/). 


## Setup

* Your client _must_ have a `.p4config` file in it's root directory.
* You should execute `p4 login` before using this client
* Right now, this does *not* tweak read-only status. You probably want `allwrite` on your client.

## Running

Typical runtime:

    fsclient -w ACTUAL_WORKSPACE_DIR -m PATH_TO_MIRROR
    
Both locations *must* exist before running. 

If you're done, make sure no app is referencing files in the mirror, then unmount it:

    umount PATH_TO_MIRROR
# Change User Description Committed
#2 16208 tjuricek Naive implementation that adds guesses at rename and unlink abilities.

It's becoming *very* apparent that we need a different approach to handling file system events. We likely need to create a log of "here's what I've done" and then after a certain period of time trigger a system that allows you to possibly just reconcile the changes. Matching filesystem calls to p4 commands ends up with *a lot* of p4 commands.
#1 16129 tjuricek Rename/move files again...
this time to the hyphenated-approach.
//guest/tjuricek/file_system_client/main/README.md
#1 16119 tjuricek Rename/move to meet workshop project conventions.
//guest/tjuricek/fsclient/README.md
#1 16118 tjuricek FSClient initial version: handles add, edit

This is a proof-of-concept app that mirrors an existing Perforce workspace to handle running commands like "p4 add" and "p4 edit" automatically when your apps add and write files.

See the readme for more information.