Following on today’s handy tips that I have commonly had to employ when dealing with fresh PC installs, I present PyDropboxPath.

As Dropbox doesnt let you rename the root folder your files are stored in on windows (Defaulted to “My Dropbox”) there are occasions when you want to choose a different name. In particular when you are running Bootcamp on a Macbook Pro with a drive shared between Windows and OSX.

Luckily some clever Python developer on the Dropbox Forums came up with a little tool that lets you rename said folder.

Again im just copy / pasting the install instructions directly from the forum (replacing the download link for the file):

Dowload: PyDropboxPath_082

Tested on Ubuntu Jaunty, Windows XP Pro and Windows7 x64 RC. Others tested on OSX and told me it was OK too

Feedback welcome.

IF IN DOUBT, DO NOT USE and ask here first.

If it breaks up somewhere, please post here.

The old terminal 0.7.1 version is in a subdirectory, only use it if you do not have wxpython and your system paths have no non-ascii characters.

The windows (EXE) terminal version needs msvcr71.dll, and the EXE GUI version needs msvcp71.dll – It’s on the download list if you don’t have it.
If the GUI version generates a error log file telling
EOFError: EOF when reading a line
then you probably are missing the msvcp71.dll.

WARNING: If you change the dropbox folder name to a root of a drive (Like, from “C:\My Dropbox” to “D:\”) or you will miss key features like sync icon overlays and right-click context menu items – good ones like “share this folder” and “copy public link”. If you are okay with this, everything else works fine.

Note: I initially named the script ‘DropboxPath’ but there is one .NET app that does the same thing in the wiki with that name. From now on, the name is ‘pyDropboxPath’.

So at first I started looking at backup tools, these seem to fall into two categories, ones that backup locally to other hard drives and networks and ones that backup to ‘the cloud’.

Now the situation is that on the Mac I have to run parallels for WindowsXP as FlashDevelop only runs in windows and the project files must be stored on the ‘local windows disk’ for the project to work properly in FlashDevelop. So the situation is I have three sepparate ‘locations’ where I need my files backed up from:

At first I played around with a few locally backing up solutions that required the machines to be on the same network. The issues with most of these was the fact that they either created temporary ‘sync files’ that reside permanently in the folder you are backing up (synctoy).

Other factors caused me to quickly look at the alternative method which is syncing your files with the ‘cloud’ which then means you can sync the cloud with all your devices.

Now there are several differnt providers out there for doing this. Ill list them in the order I discovered then and then subsequently tested them.

The Alternatives

SpiderOak was the first one I came across and the one that initially peaked my interest. It appears to be the new kid on the block when it comes to file and folder syncing. These are some things I liked and disliked about it:

Syncs based on a timer rather than constantly checking your files for updates.
Selecting files and folders to backup is hideously slow and results in many frustrated clicking (buggy interface).
Buggy uploading and syncing, sometimes you cant tell whats chewing your bandwidth or what is going on behind the scenes.

Ironically I read about Dropbox from the SpiderOak press release, in which they boast themselves superior to their nearest competitor DropBox. DropBox seemed to me like a much more mature solution than SpiderOak.

Simple to use interface (intergrates directly into the filesystem)
Has a very clever delta-file change system that is system-wide.
File version, this is great if you mess-up as you can roll-back to a previous version.
Simple to use interface. This is what I like to call the “Apple Effect”, it may be easy to use but sometimes you want more options and settings to control how the app functions.
Only one “dropbox” so only one root folder can by synced. This is a BIG issue and the one in the end that turned me off DropBox. I know that you can setup symbolic links so that you can sync external folders but I found this to be error prone and hacky at best.

Live Mesh is Microsofts offering to file and folder syncing problem. I actually heard about this a few years ago and even used it quite abit, but mostly for simple file sharing and using thier unique VNC remote desktop ability (great for accessing the home PC from work). I recently rediscovered it again while on this crusade and decided to give it another go for my new purposes.

Includes remote desktop (VLC)
Is Microsoft and hence dont get on with other platforms. Although there is now a Beta Mac version of LiveMesh im dubious as to how often this version of the software will be updated, and as I am working across Mac and Windows I need it working on both.
No delta-file sync. This is the killer for live mesh for me. All changes to a file, no matter how small, cause the entire file to be re-uploaded.
5GB limit

SugarSync is the solution I am currently using although it isnt perfect it seems to fit the bill on most counts so far.

A good payment system ($5 per month for 30gb)
Intergrates nicely with the OS on Windows and Mac
Nice interface consistent accross platforms.
Can prioritize which uploads get done first.
Cannot sync folders to within other folders.
Is buggy and sometimes corrupts files. This is my MAJOR gripe with SugarSync right now. There are some very obvious bugs that havent been addressed.

The Perfect Solution

From my adventures I have learnt alot about the state of play in the syncing arena. Each of the solutions have their positives and negatives. Currently SugarSync is winning for me, but DropBox is a close second, if only they would allow you to sync folders that dont reside within the dropbox folder.

My ideal syncing app would have the following features:

A structured pricing plan where you only pay for the space and/or bandwith used
More control over when files are synced (simmilar to SpiderOak) where you can set how often files are updated to server. This is important as when coding your published file (be it an EXE or SWF or whatever) will change often and hence may need to be uploaded to the server very often and costing alot of bandwith.
A method of excluding certain files and folders or file types from syncing. SVN lets you do this, good for excluding those temp files that change alot.
A good delta-file-change upload system, see DropBox for an excellent example of how to do this right. This method of delta-syncing means that you can potentially sync massive files almost instantly.
A method of sharing your syncs with other devices that dont belong to you (your friends computers) or potentially with people who arent even using the syncing software (web-based-access).
A good versioning system, including one click file and folder roll-backs.
A method for controlling how much bandwith is used when uploading / downloading and the ability to pause syncing.
When syncing temp files are created and then the data is filled in. This stops occasions when one device is uploading and another reports that a folder is fully synced.
OS and File-system integration.

This is certainty not an exhaustive list but merely the main points that I can think of right now. I think there is definitely room for improvement in this area and the current solutions havent fully realized their potential.