Short answer ...
My suggestion: Start with public accounts on GitHub and/or Bitbucket (other?). Throw up a few public projects and start using the tools/interfaces. Once you've got a feel for the services, then you should have a grasp as to what the limitations, advantages and disadvantages of each service are. From there, you should be able to choose the best path to version control enlightenment. :)
Long answer ...
I don't currently have off-site backup for most of my code, so as part of this, I originally thought I would upload all of my personal projects, or at least all of my iOS projects, to a private GitHub-hosted repository. However, I have a lot of projects sitting around, many of which are fairly low-value (i.e., adapted from books and written for the learning experience).
Have you considered installing your own Git client? If you're already paying for web hosting, then it might make sense to use that host for your own Git setup.
For example, my host is WebFaction (no affiliation):
Installing the Git Web Application
Heading this route might allow you to save some $$$, esp. if you're already paying for hosting.
Not only does GitHub charge by the private repository,
Just to clarify for others (again, no business affiliation to GitHub or BitBucket):
- $7/mo. for up to 5 private repositories, unlimited everything else.
- $12/mo. for up to 10 private repositories, unlimited everything else.
- $12/mo. for up to 20 private repositories, unlimited everything else.
Note that "Business Plans" pricing is different.
As stated in by Andrew in the other answer, Bitbucket touts unlimited private repos.
- 5 users: Free
- 10 users: $10/mo.
- 25 users: $25/mo.
- 50 users: $50/mo.
- 100 users: $100/mo.
- Unlimited $200/mo.
it doesn't seem to have any way of organizing repositories hierarchically.
Not sure exactly what you mean by "hierarchically" (probably because I'm not familiar with SVN).
I'm not sure if this would help, but you could look at this comparison table to see how the commands compare/differ:
Is there something I'm missing that would allow me to use a git repository with a hierarchy and check out pieces as I need them / work with them, the way I currently do with SVN?
Does GitHub (or a competitor, like BitBucket) have some project organization features that I'm missing?
Not sure if this will help, but you might take a look at:
Git comes with built-in GUI tools for committing (git-gui) and browsing (gitk), but there are several third-party tools for users looking for platform-specific experience.
... again, not sure if any of those tools could help you to get a feel for what's possible.
To be clear, I'm not sure of you Git skill level ... if you're new to Git/GitHub, using a GUI might be a quick/easy way for you to get a feel for things. I personally like using the official GitHub for Mac/Windows apps.
Failing that, what's the generally accepted "git way" of handling this situation (discard projects not intended for release, store them offline, bundle them together somehow, etc., etc.)?
If I were you, I'd be using repositories.
How many private repositories do you need?
If you want to use GitHub, one solution might be to get the cheapest plan and utilize a few private repos to hold all of your test/non-public code. You could just use a folder structure on your
main branch to maintain a hierarchical structure, or you could use multiple branches to keep things more separate.
Tip: If you're using a more recent version of Git, you can pull specific branches using
git clone -b mybranch --single-branch git://sub.domain.com/repo.git:
I have to warn you though, using branches to organize code (like folders) isn't really the best way to do things (though, there's nothing that says you can't head this route).
(Seem my answer here for related info in regards to GitHub branches.)
Again, I think multiple repos are the way to go.
You might ask yourself if your code is really needing to be private; is it possible that you could go public with said code without any repercussions?
Put libraries on GitHub, continue hosting my own SVN for all other projects, use a non-VCS solution for off-site backup (blech),
If you head this route, Dropbox (or similar) might be a good way to get some form of version control and syncing for your off-site backup.
Put libraries and software I plan to release on GitHub (as public and private, respectively), continue hosting my own SVN for projects I don't care about as much and am only likely to revisit to refresh my memory on how to implement XYZ, decide that I'm willing to write them off if my house implodes (double blech),
This takes me back to the question "Do you already pay for hosting? If so, you could install your own Git host"; the advantage being, you could have all source code under the Git umbrella, even if it's not all on the same host (i.e., use GitHub for the public stuff you want to show off).
Put everything on [GitHub and/or BitBucket], deal with having some ridiculous number of repositories by searching for what I need / maintaining some offline set of pointers into my [GitHub and/or BitBucket] account (triple blech)
---> See my short answer above. ^^^^^^