3 ms·
You have only two other options: * use one domain for your marketing site and another for the app (not desirable) * incorporate your marketing site into your
by delano 16y ago
You have only two other options:
* use one domain for your marketing site and another for the app (not desirable)
* incorporate your marketing site into your rails app.
BTW, thanks for the Particletree link. I hadn't read that.
- marcamillion 16y agoWell....I guess the real question should have been, what are the options and the related pros and cons. I know I said I don't want the app to be on the same domain as the marketing site...but that's based on my limited knowledge. What are the pros & cons (both technical and non-technical) that I should consider with this option - and all other options. Thanks.
- bobbywilson0 16y agoI think the thing to consider is what is most practical to your users. I want to be able to login at yourdomain.com I don't want to remember that I have to login at app.yourdomain.com. I think ultimately providing the simplest path for your users to sign up and log in with is what you should do. What might make the most sense is putting your marketing site in a sub-directory like /tour or something and then get another domain just for marketing that redirects you to the /tour marketing page.
- marcamillion 16y agoThis is an interesting solution. So the actual app could be at my main marketing domain - perhaps just simply have the marketing site appear when they are not logged in. Once they are logged in, they are shown their home screen. But how do I handle the file organization for each user. Give them their own subdomain or just do folders? So all the images for marcamillion would be mydomain.com/marcamillion/images, and my home site would be mydomain.com/marcamillion.
- bobbywilson0 16y agoYeah, the style you mentioned (domain.com/user/images) makes sense to me, and it is built into Rails to do it that way.