#general
- h
happy-kitchen-89482
05/01/2016, 10:57 PMAlthough broken is worse - h
happy-kitchen-89482
05/01/2016, 10:59 PM - h
happy-kitchen-89482
05/01/2016, 10:59 PMHmm, looks like CloudFlare can give us ssl support for this - h
happy-kitchen-89482
05/01/2016, 11:00 PMEh, but it’s not secure between cloudflare and github - a
ancient-stone-50795
05/01/2016, 11:01 PMWell, we could just checkout the code and manually sync it. The problem is, it will probably take time for DNS to propagate if you want to transfer the CNAME to another domain. - h
happy-kitchen-89482
05/01/2016, 11:04 PMI don’t think we’re going to do that right now, it’s either leave things the way they are, or kill the CNAME record - h
happy-kitchen-89482
05/01/2016, 11:04 PMAnd go back to pantsbuild.github.io - h
happy-kitchen-89482
05/01/2016, 11:04 PMWhat would it take to host it ourselves? - h
happy-kitchen-89482
05/01/2016, 11:04 PMNot that we can do that by tomorrow - h
happy-kitchen-89482
05/01/2016, 11:05 PMWe could do this: - h
happy-kitchen-89482
05/01/2016, 11:05 PMcreate a second github pages repo - h
happy-kitchen-89482
05/01/2016, 11:05 PMSend the CNAME to there - h
happy-kitchen-89482
05/01/2016, 11:06 PMbut have the old one available at pantsbuild.github.io - h
happy-kitchen-89482
05/01/2016, 11:06 PMSo that both domains work - a
ancient-stone-50795
05/01/2016, 11:08 PMI think we should go ahead and add the -L to the instructions so that we can redirect that URL when we need to. - a
ancient-stone-50795
05/01/2016, 11:08 PMIf we host it ourselves I say we just keep the existing pantsbuild.github.io repo but just have our new webhost provider sync to master on the same repo. - l
limited-country-20626
05/01/2016, 11:16 PMnvm - just behind the pull reuests - l
limited-country-20626
05/01/2016, 11:16 PMI see - l
limited-country-20626
05/01/2016, 11:17 PMfsqio was getting version mismatches - it was really throwing me off with four different versions! - h
happy-kitchen-89482
05/01/2016, 11:20 PMOh, hm, you can only have one github pages repo per org, unless you’re willing to have the repo name be in the url - h
happy-kitchen-89482
05/01/2016, 11:21 PMwe can’t have foo.github.io unless we create a foo user, but we can have pantsbuild.github.io/foo - h
happy-kitchen-89482
05/01/2016, 11:35 PMOK, I have a temporary solution - h
happy-kitchen-89482
05/01/2016, 11:36 PMI’ve published the docsite to benjyw.github.io, and will redirect the CNAME to there - h
happy-kitchen-89482
05/01/2016, 11:37 PMthat way pantsbuild.github.io will continue to work (with https) but the pantsbuild.org links will still work (with http) - h
happy-kitchen-89482
05/01/2016, 11:37 PMthis’ll tide us over until we can host our own ssl cert etc - h
happy-kitchen-89482
05/01/2016, 11:37 PMI will give everyone commit privs to benjyw.github.io, and modify the publish script appropriately - h
happy-kitchen-89482
05/01/2016, 11:37 PMSound OK? - a
ancient-stone-50795
05/01/2016, 11:44 PM@happy-kitchen-89482: Is that going to solve the cert problem? Still don't think its a great idea, the CNAME could take a long time to propagate. - h
happy-kitchen-89482
05/01/2016, 11:44 PMIt will restore the status quo ante - h
happy-kitchen-89482
05/01/2016, 11:44 PMi.e., https will work on pantsbuild.github.io