3 ms·
I 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 logi
by bobbywilson0 16y ago
I 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.