862911 - come up with a way to map old Thimble page URLs to our new solution

Status: RESOLVED DUPLICATE of bug 880768

(Webmaker Graveyard :: Thimble, defect)

Comment 1

[Brett Gaylor [:brett]]

devil's advocate - im ok with that not being the case, ie that those old thimble pages stay where they are, but we don't try and have them forkable etc.

Solution is for users to cut and paste :)

Comment 2

[Pomax]

I like the way you think, although we didn't use S3 before, so the "old pages" actually live "through" old thimble right now. We could keep that live as only a content-serving system for a while and then phase it out as more people use the new and improved flavour of webmaker?

Comment 3

[Brett Gaylor [:brett]]

yes.  keep it alive only as needed.  ensure that people who try and use the actual app go to the right place.

Comment 4

[Pomax]

the old (current) thimble hosts its pages on /p/... so that should be easy enough to reroute; I ask around to see if we can keep old thimble up in parallel as a "reachable thing" for seeing pages, while turning off its publication once we switch over to new thimble.

Comment 5

[David Humphrey (:humph)]

Should we auto-publish all the existing content to S3, reserve something like thimble1 on the new webmaker and do a 300 to redirect from thimble.webmaker.org/p/* to thimble1.[new-publish-domain].org/* ?

Comment 6

[Pomax]

that would be an excellent idea. 301 I assume?

Comment 7

[Pomax]

this has effectively become a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=880768