It's been awhile since I had to hit up the Tech & Help folks with a Ravenwood related question. I've been saving it up for a good one, so here goes.
Here's our current setup: I have a server located in my home office (built with help from you guys!). Our business files live on this server. I occasionally need to access some of those files remotely, say from the office at my day job. There are also files that both MonoCheli and I need to work on, schedules and what not. We currently use DropBox to meet both of those needs. We have several dropbox shares set up: one that is accessible on our main castle computer (staff can see) and can be seen by any of the management team on any of their computer, one that is accessible only to the management team, and one that is accessible only to me and my wife.
This setup works, but is currently posing us three problems. In descending order of import they are:
1) If you are actively working on a file in Dropbox, every time you change it or your program auto-saves it, the entire file is re-uploaded to Dropbox. Given our severe bandwidth limitations, this is causing an issue for any files that MonoCheli needs to work on.
2) All of the files included in Dropbox are physically located on my office computer. This isn't a huge problem, but having Ravenwood files on a computer that isn't Ravenwood controlled does make me somewhat nervous.
3) We are ending up with multiple copies of files that are in Dropbox, as those files need to be in Dropbox for accessibility, but also need to be on the main file server in their appropriate workspaces.
I think the solution is at least partially in some form of VPN being run from my home server. Perhaps a router such as this one with built in VPN capability? That would allow me to access the files remotely without actually syncing them to the local machine, solving problem #2. MonoCheli would be able to work on the files he needs, then upload them via the VPN once he's completed them, solving problem #1, although in a clunky way. It also helps with problem #3 as the files would live on the server alone, except for the in process files MonoCheli is currently working on.
Am I on the right track, or is there a more elegant solution that I'm just completely missing?