Docs for Spock-api-ghcjs missing

[Profpatsch]

(Original title: docs for Spock-server-api missing)

Hackage isn’t building and there are no docs on the AWS instance (like for Spock and Spock-api).

[agrafix]

It's all there?

https://spockdocs.s3.eu-central-1.amazonaws.com/Spock-0.11.0.0/Web-Spock.html

https://spockdocs.s3.eu-central-1.amazonaws.com/Spock-core-0.11.0.0/index.html

https://spockdocs.s3.eu-central-1.amazonaws.com/Spock-api-0.11.0.0/index.html

Am 19.09.2016 um 23:58 schrieb Profpatsch [email protected]:

Hackage isn’t building and there are no docs on the AWS instance (like for Spock and Spock-api).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Profpatsch]

Ah, I mean the docs for Spock-server-api. Wrong formulation.

[agrafix]

It's right there: https://spockdocs.s3.eu-central-1.amazonaws.com/Spock-api-server-0.11.0.0/index.html ;-)

[agrafix]

Here's the whole ecosystem: https://spockdocs.s3.eu-central-1.amazonaws.com/index.html

[agrafix]

Only the docs for Spock-api-ghcjs are missing, which is essentially:

https://github.com/agrafix/Spock/blob/0.11.0.0/Spock-api-ghcjs/src/Web/Spock/Api/Client.hs#L27-L40

[Profpatsch]

Oh, I see.

[Profpatsch]

Maybe you could give docs.spock.li a DNS entry to the AWS server.

[agrafix]

Yeah, the problem is that HTTPS won't work anymore with plain S3 if you use custom domains. The options are to configure CloudFront in top of S3 or just a plain simple redirection.

[agrafix]

Maybe another way to approach this would be to get the Hackage-Docs working again. This is probably currently timing out because the package constraints are not "good" enough...