Backing up your code to the cloud [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 10 years ago.

I want to backup my code regularly to the cloud.开发者_C百科 What's the cheapest and easiest way to do this for a single developer? I was thinking of running my code completely from a DropBox share (continuous synchronization with their free storage plan), which seem to meet the requirement of cheap and easy -- but, any problems with this idea?

---

Use Git for source control and get yourself a free (or $7/month if you want private repos) GitHub account (an online repository where you can push your changes).

This way you'll get the benefits of a modern source control system, plus free online backup and online availability of your source code.

Even for a lone developer a source control system is advantageous e.g. history auditing, change annotation, change grouping, rollback, branching, etc. Dropbox is likely to be pretty unsophisticated in these respects.

---

I use iGoUSB for my backup needs. It has a very cool versioning system with snapshot history that will allow you to go back at any (backup) date to recompile your code. Now, this with dropbox works PERFECTLY:

• Dropbox keeps your code safe for as long as their service runs
• Dropbox 2GB free storage should be plenty for source code needs
• iGoUSB backup repository will let you go back in time whenever you need (which complements the 30 days back that Dropbox gives you for free) - instant versioning!
• iGoUSB allows backup from multiple computers/profiles - so you can save your code from any computer you use
• igousb will save only the changed files (while keeping code structure snapshots intact) and for source code files the whole backup will take only a few seconds!

This combination will allow you to:

1. backup your sources from multiple computers
2. keep your code safe
3. keep a transparent and really easy to use versioning system

Just add your favorite editor and tools (anything like notepadd++ and winmerge) and you have an enviable portable solution ready to use anytime you like :)

Note: igousb is not free, you might get a discount if you're a student, but at least it's only one time pay and you might need a good and portable backup tool anyway.

---

It seems like a good idea to me. A friend of mine hosts a website through dropbox and he said it's up most of the time, but occasionally it will be a 404 error and you have to refresh. np.

There's github and google code if you don't mind sharing your code.

If this is the route you want to take and you want to keep it to yourself, I'd recommend using git for local and remote version control, and keep a copy on dropbox.

---

http://www.fogcreek.com/kiln/

Joel better +1 me :)

---

There's not a lot of problems with using dropbox if you're going to continue being the sole developer of the project. For backup purposes, it's just fine. But you may want a source control system for keeping revisions and rolling back if you mess something up. xp-dev have got good private repositories for svn or git hosting depending on which you prefer.

---

I'm not going to tell you which source control system to use, that's up to you, but you really should be using some type of source control. Here are a few that have been known to work well:

• Subversion
• Git
• Mercurial

If you choose either of the latter options, you can make use of free hosting at GitHub or BitBucket to host your data in the cloud.

If you decide to use BitBucket as a solo developer, you get unlimited public and private repositories for free. In the comments, you mentioned that you were concerned about code compromise, so access to private repositories might be important to you.

The idea of continuous synchronization through Dropbox, while marginally easier, loses the immense benefits of revision control, and is not recommended.