Ask HN: good place to store code online?
what is the best place to store code online?
i want to have a backup of my files somewhere in case something happens and an emailadress is just annoying for this kind of thing.
i could use google doc to save the soource code but i just want to be able to store it as a .py-file or .scm-file and download directly later.
mozy seem to cost even for the smallest storage? xdrive has 5GB free though.
any tips? should obv support any fileformat.
45 comments
[ 96.5 ms ] story [ 868 ms ] threadlooks very good though, exactly what i want. fast simple and free(?).
We used to use their entire package (bug reporting, trac, etc.) but now we're only using them for SVN and use locally-deployed software to manage the rest of the toolchain (mostly Atlassian software such as Jira, Confluence, Crucible, and Fisheye)
and 500MB of free space is great too!
Somewhat recently, we switched to git and started hosting ourselves, but you might look into code.google.com .
If you don't actually want your code to be public, just get some free online storage. Do you really need more than 5GB?
I once had my SVN with them; you have no control over availability - and availability wasn't good, in my experience.
My backup job runs from home using a scheduled script (cron, tar, scp).
You could just as easily send your tar files to Amazon S3
http://www.beanstalkapp.com/
I highly recommend it.
You get root access, so you can do whatever you want with it. They're great for prototyping web apps.
I like Slicehost (as low as $20/month) http://www.slicehost.com/
http://mozy.com/free
I paid for 2 years upfront and got a 50% discount - total price was ~$12/month for a Xen instance (debian) with 256MB Ram
I have SVN/trac on it ... although, I've been thinking of migrating to git.
I also use it to host a lot of other stuff too.
It encrypts the directory name and adds a timestamp, to make a filename that reveals nothing about the contents of the file except for the time it was created. It stores the original directory name along with the encrypted directory name in a local log file, so I can tell what's what later.
Then it zips the directory and its contents into a file, names it with the encrypted filename, and does a GPG encryption of the file.
Then it uploads it to Amazon S3 and cleans up after itself.
All of this is completely automated once I type in the command. I do it for my project directory, which contains all my projects for the calendar year, periodically. After the year closes out, I start a new year and the old files (from previous years) stay safe and unchanged on S3.
Over the course of a year, if a few backups for the same year pile up, I usually delete the old ones. I haven't automated that part.
This scheme is OK for backing up a few important directories, if they aren't large, like for source code, just what you asked about -- a few hundred megabytes will cost just pennies a month on Amazon.
It's not a SVN or GIT solution, but it gives you total privacy, rather than relying on a third party to do the encryption for you.
Seriously, though, thanks to everyone recommending GitHub. We're constantly trying to improve our service to remain the best (even if we're the only one) Git host.
Your code is everything. You should take care of it properly.
On the other hand, if you are working on OSS, then of course your need for privacy is trumped.