Add "redirects" configuration about superstatic HOT 9 CLOSED

Note that this requires a new route parsing rule: colon-based segments. We can talk about this more, but basically need to be able to redirect segments dynamically and this is the best way I can think to do it. Open to comment.

from superstatic.

What do you mean by "segments"?

from superstatic.

URL segments. So :name matches an entire URL segment and can be used in the destination.

e.g. {"/some/:path/here":"/other/:path"} matches /some/thing/here and redirects to /other/thing

from superstatic.

That makes sense. I already have a module that will make those segments very easy.

Recommendations:

1. I recommend we use the "routes" object for redirects. It already handles redirects and it's one less config object in the json file.
2. I recommend we configure status codes like this:

{
  "routes": {
    "/some/path": {
      "status": "302",
      "path": "/some/other/path/redirectied"
    }
  }
}

This makes less confusion as to where the status and the path go in the array for the user.

from superstatic.

We already handle redirects in the routing? I thought it was only rewrites. How do redirects currently work in routes?

from superstatic.

I lied. The only redirects that happen are for clean urls and directory indexes. We should add a redirects object.

from superstatic.

Yeah, and you're right it should be plural since routes is plural.

from superstatic.

NOTE: providing a url redirects to that url. Providing a path, redirects only to that path

from superstatic.

Let's do status, not statusCode. For one thing, we have generally used an underscore convention for Superstatic config, for another it's more succinct and I like it better.

from superstatic.