https (https://www.scala-sbt.org/ uses Github's cert) about website

[SethTisue]

is this the ticket of record on ''Google results are returning HTTPS instead of HTTP now, but the certificate is for github, not for scala-sbt"? /cc @Ichoran

[dwijnand]

Alternatively we could reverse things and redirect from scala-sbt.org to (I guess) https://sbt.github.io/website

[eed3si9n]

We can probably use https://www.cloudflare.com.

[dwijnand]

Sorted: https://www.scala-sbt.org/

[dwijnand]

steps to migrate back to GitHub (from isaacs/github#156 (comment)):

1. Remove the CNAME from the old repo.
2. Make sure your DNS is directed directly to GitHub pages and not a CDN.
3. Create a new repo with a different name.
4. Push your files to this new repo. DO NOT push the CNAME file with this. If you push the CNAME file here, enforce HTTPS gets disabled.
5. Now go to settings for the new repo and enable GitHub pages. Wait for the site to build and check.
6. Now add a CNAME through the settings.
7. Wait for HTTPS to set up (takes ~2 minutes) and have fun!

[eed3si9n]

I didn't know about the Google part.

[eed3si9n]

Maybe it's time we consider moving to somewhere else like S3.

[Ichoran]

My first hit on Google for sbt subproject is

sbt Reference Manual — Multi-project builds
https://www.scala-sbt.org/0.13/docs/Multi-Project.html
Each subproject in a build has its own source directories, generates its own jar ... as the subproject's ID, which is used to refer to the subproject at the sbt shell.

I get similar results with other queries.

[dwijnand]

Oh actually I guess it's simply https://sbt.github.io

[dwijnand]

GitHub has started rolling this out: isaacs/github#156 (comment) so we could switch back to them.