Migration to GitHub Pages

[raimis]

In preparation to the new website (#45), we need to move to the GitHub Pages (https://docs.github.com/en/pages). Apparently, even the current (old) website works fine on the GitHub Pages: https://openmm.github.io/openmm-org/

To complete the migration, the DNS record of openmm.org has to be update: https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain

As a bonus, this will solve the HTTPS issue (#38).

[raimis]

@jchodera, as I remember, you have access to the domain records.

[jchodera]

Yes! I can do this if we're ready to go!

@peastman @Yoshanuikabundi : Do you think we're ready to go now?

[peastman]

I did a quick check of the github pages version of the site and didn't notice anything that looked broken. If anyone else wants to do their own check, that would probably be good. If no one sees any problems with it, I think we can switch to it.

[jchodera]

The only thing I noted is that the Markdown renderer does not do syntax highlighting, but this is minor and something we can fix.

Thanks so much for all the effort you put into this, @raimis! I'll switch this today and report back!

[Yoshanuikabundi]

Looks good! The docs are still served over HTTP rather than HTTPS, so they're not being rendered with GitHub Pages - I'm sure you all know that but I'm mentioning it in case it suggests to someone with more knowledge about how everything is served that something is wrong.

[jchodera]

The docs are still served over HTTP rather than HTTPS, so they're not being rendered with GitHub Pages - I'm sure you all know that but I'm mentioning it in case it suggests to someone with more knowledge about how everything is served that something is wrong.

@Yoshanuikabundi : That's a great point! Can you open an issue to remind us about this?

[jchodera]

@peastman @raimis I'm starting the DNS migration/update now.

[jchodera]

Migration complete! Let me know if you notice anything broken with the DNS.

For reference: I've deleted the AWS Route 53 zone that was previously serving our DNS and switched to GoDaddy's DNS servers, following the instructions linked by @raimis to activate custom GitHub Pages domains.

[jchodera]

It looks like everything at docs.openmm.org (which is still hosted on S3) appears to be broken.

Let me see if I can fix that with GoDaddy's DNS. Otherwise, I'll migrate back to Route 53 DNS and just serve DNS from that.

[jchodera]

For reference, here are the old AWS Route 53 records:

And here are my updated GoDaddy records:

I'm still seeing issues with docs.openmm.org and the docs pages within, but I'm not sure if this is due to (1) DNS propagation delay, (2) the docs pages specifying a root URL that is on a different site, or (3) something else I don't know about.

I'll revert this change if the DNS doesn't pick up and fix things in 30 min.

I've already tweeted about the disruption:
https://twitter.com/openmm_toolkit/status/1396942413449498624

[jchodera]

Looks like this is not working at all now, so I will likely need to revert back.

[jchodera]

openmm.org is working now that I've changed the GoDaddy records, but I'm still not able to get the docs pages to work:

Any ideas?

URLs like http://docs.openmm.org/latest/userguide/index.html are not correctly being redirected to http://docs.openmm.org.s3-website-us-west-1.amazonaws.com/latest/userguide/index.html

[peastman]

The docs are working for me. I don't know whether that's because something cached somewhere hasn't propagated to me yet, or because you needed to wait a little longer for a cache to update for you. I'll check again in a little while and see if it's still working.

[jchodera]

OK, they started working when I made this change:

It looks like they're still not https, however.

[jchodera]

Closing this since migration is complete, and http/https issue is separated into #50.

[raimis]

builder.openmm.org seems to be broken:

$ curl -I builder.openmm.org
HTTP/1.1 400 Bad Request
x-amz-error-code: IncorrectEndpoint
x-amz-error-message: The specified bucket exists in another region. Please direct requests to the specified endpoint.
x-amz-error-detail-Endpoint: builder.openmm.org.s3-website-us-east-1.amazonaws.com
x-amz-request-id: ZM8ATANR65YABFH0
x-amz-id-2: raG/lgw3wiC++jGCCDwbXDA+Ls9Pmrgjiu644hRtnbhgvMUDT54iiVAPEbDel4wXP9Vu3JNKSlU=
Date: Wed, 26 May 2021 09:48:24 GMT
Server: AmazonS3
Connection: close

This might be not a DNS issue.

[peastman]

Where did you find a reference to builder.openmm.org? It hasn't been supported in many years.

[jchodera]

I spotted an error in the DNS entry. I've made the fix, and we'll see if it starts working soon.

[jchodera]

http://builder.openmm.org is working once again! The issue was that the DNS entry was pointing to a bucket in the wrong region. For some reason, builder is in us-east-1 and the docs bucket is in us-west-1!

Please reopen if this is not resolved.

[peastman]

Please make it stop working again! Like I said, it hasn't been supported in years. Where is it being served from? We should track it down and, if possible, take it down.

[jchodera]

Whoops! Next time, could you be explicit about what you think the intended behavior should be, @peastman?

How would you like me to deactivate it?

1. Remove the DNS entry and tweet that we are no longer supporting it
2. Blow away the S3 bucket containing it as well
3. Something else?

[peastman]

Remove the DNS. I don't think there's anything to tweet. We haven't supported it in many years. It's been a long time since it actually produced correct code. So far as I know, we removed all references to it from our website years ago. That's why I asked @raimis how he even knew it existed. Where did you find a reference to it?

[raimis]

That's why I asked @raimis how he even knew it existed. Where did you find a reference to it?

@peastman, it shows up frequent, if searching something about OpenMM on Google.

[jchodera]

@peastman : I've deleted the builder DNS entry and deleted my tweet about having fixed the builder following DNS migration.

What should we do about the frequent search hits?

[peastman]

How very annoying! Let's make sure none of our websites have links to it anywhere. Once the URL no longer works, hopefully Google will figure out quickly to stop directing people to it.