Support for site redirects and aliases

[dhedlund]

Redirect

If the location of a calendar moves, we need a way to automatically take people to the new location of that calendar. The URL of the calendar in the user's browser should change to the new or correct URL using a redirect and any additional path parts and parameters should be retained. Examples:

• Rename sfbay.activatehub.org/startup/events/6 to sfbay.activatehub.org/tech/events/6
• Redirect commonly logged typos such as /art to /arts
• Redirect pdx.activatehub.org to portland.activatehub.org

  Alias

If a site has a vanity URL or domain, it would be nice for people to optionally use that to access the site. Aliases should not redirect to the real calendar, but rather pretend that the calendar is at the aliased URL. Examples:

• Alias activatepdx.org to portland.activatehub.org

  Implementation

The domain and _siteprefix attributes of the Site model should be moved into a SiteURL model that has a Site.has_many :SiteUrls relationship. The domain and site_prefix can be combined into a single attribute called url or base_url. The new model could also have an attribute called relationship that allows the values primary, redirect or alias. With this information, the ApplicationController should be able to determine whether to redirect the user to the primary site URL or handle the request normally.

[techieshark]

A quick fix would be to redirect activatepdx.org to portland.activatehub.org (slightly different effect from what is described, but better than current behavior).

[lindsaycaron]

Rock. Peter, can you make that quick fix redirect?
Also, in WordPress adjustment, pointing the ActivateBay logo to sfbay.activatehub.org/startup