Closed carols10cents closed 11 years ago
Why would it not work? I have several running on a couple of subdomains. I'm not sure how you would be able to introduce a regression either.
lol. i was sleepy and being stupid while working on https://github.com/hotsh/rstat.us/pull/720... i think i've figured out the right way.
I still have some concerns about nodes using optional www, since ostensibly you could follow someone@www.whatever.com OR someone@whatever.com, and right now we're looking at the root_url to see if we're on the local node, which could ALSO be www.whatever.com OR whatever.com.... but oh well. we'll deal with that when someone complains.
A relic of the internet, I'm afraid. Generally should discourage www as a subdomain for nodes. Use 'status' or something.
If they indeed point to the same XRD for the site, the template would have to produce a canonical subdomain to retrieve user information consistently. The app would have to be configured for that, but a dns redirect and reading the response subdomain would also suffice.
I very much dislike the fact that rstat.us enforces the www.
Do we support installation and use of rstat.us on a subdomain (such as rstatus-staging.herokuapp.com)?
I think I may be about to introduce a bug having to do with this, while working on the PR for Issue #698 that checks if we should look at the users on the current node or not... I'll explain more when I get that in.
I wouldn't be surprised if there were other issues with running on a subdomain though, since I don't think it's been thoroughly tested.