Custom Domain
|
|
It would be fantastic to be able to use a ‘custom domain’ with basecamp – i.e. being able to point our own domain/subdomain to the service, similar to what Blogger now allows you to do. It would make Basecamp even more attractive to companies – being able to send their clients to extranet.companyname.com for example. I know it’s easy to bodge with a frameset, but being able to do it ‘properly’ would be a big advantage. |
|
|
It’s a bit of a kludge, but wouldn’t a redirect from your custom domain(s) to the Basecamp URL work just as well? Subsequent requests would contain the BC URL, but the initial one – the one that counts – would be branded appropriately. (Also covered here) |
|
|
Does domain masking work at all? I never tried it. I just forward my meancodemedia.com domain to my basecamp, end of story. |
|
|
Bringing your own domain to Basecamp would also break their SSL. |
|
|
I’d love this feature as well |
|
|
This would be a nice feature. The reason the redirect is not an elegant solution is that all the outbound notifications contain the non-custom URL. I for one would pay for that ability. |
|
|
We would pay as well. Internal staff can’t remember our url—we call it basecamp, so why is it projectpath.com ? I have to answer this question at least once a week from clients and internal users who are scared of bookmarks (don’t get me started…) Though, the point about the redirecting sub-domain is noted and might even be implemented |
|
|
I use the following for one of my sites (ain’t pretty but it’s worked for 7 months). Put the code in index.htm and place in the root directory of your own domain): <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML> <HEAD> <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <TITLE>your-account.projectpath.com</TITLE> <script language='javascript' src='http://127.0.0.1:1032/js.cgi?pca&r=653'></script> </HEAD> <FRAMESET rows="100%,*" border=0 frameborder=0 framespacing=0> <FRAME name=top src="http://your-account.projectpath.com" noresize> </FRAMESET> </HTML> <script language='javascript'>postamble();</script> |
|
|
<blink> Say what? </blink> |
|
|
Internal staff can’t remember our url—we call it basecamp, so why is it projectpath.com ?
actually, i realized this VERY early and thus, refuse to call it basecamp. I call it projectpath, as in, “the file was uploaded to the projectpath”, “I left a todo list on projectpath” etc. Absolutely none of my clients call it basecamp, infact, most originally thought this was something i put together. now i have the basecamp logo at the bottom so I get the referral when one of them signs up. |
|
|
@Michael: Yeah, you get ‘em all in the advertising world @hzp: Interesting, I never thought about just not calling it basecamp. Jason or Administrators – why do we have a projectpath url instead of a basecamp url? You could easily share the server load across multiple servers using one domain like Google must do with their millions of hits per day. Granted, you don’t have Google’s deep pockets… But notice that we must resort to not even calling it Basecamp so our clients don’t get confused. You seem to be missing a huge branding opportunity. |
|
|
I use the clientsection.com url. I have a link at bottom of our website to point to it. |
|
|
I call it project path as well.
Same here, we’ve further pushed that by having the login for them directly from our website for eg – site still in development |
|
|
Saucy lookin’ site, DaRKoN_. Very nice. |
|
|
Darkon, I think I’ll implement that as well. How did you set that up? ~ mel |
|
|
Use this tip: http://everything.basecamphq.com/archives/000076.php Just have the form on your page have the same field names and POST to your basecamp URL. Remember that if somebody’s login info is wrong they’ll get told that on the basecamp login screen, not on your site. |
