Expired SSL cert on https://progit.org/

[Graham42]

There's an SSL error on https://progit.org/ NET::ERR_CERT_DATE_INVALID

[ben]

Paging @schacon!

[schacon]

Uugggggggghhhhhh. So, this was on a DigitalOcean droplet and has not come back up well. It was way too complex so that I could run the Atlas stuff, but since that's now defunct I suppose we should simplify this and just move it to Heroku. I'll work on that asap (and add you to it, @ben). Sorry about this - it will be a day or so.

We should figure out if we want to keep doing automatic builds and if so, how we're going to accomplish it now.

[jnavila]

Deploying the html files on the site can be done the same way we were doing it for the first edition. We started a discussion at #625

The publication to pdf and ebooks is the hard spot in this.

[jnavila]

Hey @schacon What's on your mind for this? Do you need a (weak) hand? Should we try to mimic the processing for the first edition?

[crd]

I see the ebooks are hosted on s3 -- publishing to s3 is as simple as running a lambda script which is free for the first million calls. I can help with that.

[ghost]

This is still an issue. https://progit.org/ exists, but attempting to access it still results in a "certificate expired" warning as mentioned above. This might be alarming and off-putting to any Git newbies who go to that URL via bookmarks, links, or search engine hits: they might think that the book (or Git) is a dead project :(

@schacon :

• if you are planning to keep hosting content at that domain, please can set up LetsEncrypt for it, to avoid the certificate error?
• Alternatively, if you are no longer planning to host content at that domain, please can you put a redirect or suchlike in your DNS host, to take visitors to some more appropriate place, such as https://git-scm.com/book ?

Thanks :)

[KZiemian]

Should this issue remain open?

[ben]

http://progit.org now hosts some kind of magazine in French. Going to close this for now.

[crd]

I grepped the source and the original domain is no longer referenced. I agree with closing the issue. Thanks!

…

On Aug 27, 2022, 5:58 PM -0400, Ben Straub ***@***.***>, wrote: Closed #672 as completed. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>