Paths vs Subdomains

28 Nov 2010

Earlier today I put out a tweet which asked:

site.com/account (Github) or account.site.com (Basecamp) style for per-account URLs?

There were great arguments from both sides in the debate. Tweets like Darcy Laycock's and James Ottaway's.

I've decided to make it paths for two reasons.

Easier to test

Quite simply, paths (http://ticketee.com/account) are much easier to test by booting up rails server than subdomains are. They require no additional configuration by that means and they're guaranteed to work on all systems.

Subdomains on the other hand would require use of another tool such as Ghost which would work on Ubuntu and Mac OS X, but not Windows. There is no One True Solution for everybody when it comes to subdomains. Since Rails 3 in Action is intentionally written without discrimination between operating systems, I would prefer this chapter to be no exception to that rule.

Account sharing

In the application I am going to be sharing users across accounts. A user that is created on one account, can be gifted access to an alternative account. This would result in an "open" system, and I think a path URL would be better for this than a subdomain URL.

Thank you all for your suggestions and the interesting discussions tonight. You've been amazing.

blog comments powered by Disqus