Closed bbengfort closed 7 years ago
The FluidFS server/daemon will write a PID file to /etc/fluidfs or ~/.fluid/ (right now I'm sticking with home directory config, operating more closely to Dropbox) with both the process ID and a command port.
The command port will be selected using the random open port method (the default for Go's TCP comms) and the server will listen on that port on the local loopback address. The command line client will read the PID file for the port and communicate using gRPC services.
This is a pretty standard model that I've used in the past and is pretty secure (local only) but it does have one limitation - no remote c&c.
This is the process that is always on that mounts Fuse directories and listens for command line calls from the fluid config client. It will also run a simple web server for communication and integration.