Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move documentation to Paradox (#50) #51

Merged
merged 16 commits into from
Dec 9, 2016
Merged

Conversation

jonas
Copy link
Contributor

@jonas jonas commented Nov 15, 2016

The result can be viewed here: https://jonas.github.io/ssl-config/index.html

Fixes #50

@@ -47,7 +47,8 @@ sbt '+publishSigned'

echo "Publishing docs..."
sbt makeSite
mv documentation/target/sphinx/html ../releasing-the-docs
rm -rf documentation/target/paradox/paradox # Paradox site bug?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a workaround for what might be a bug in the sbt-site Paradox plugin. If I have time I will try to investigate later.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best to report on paradox repo I think. Issue is that it should have cleaned up that directory by itself right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened sbt/sbt-site#80

@ktoso
Copy link
Contributor

ktoso commented Nov 15, 2016

Wohoo, awesome :)

@ktoso
Copy link
Contributor

ktoso commented Nov 15, 2016

LGTM, lookin good.
I wonder if @2m would be able to set this up to publish docs into doc-hub?

@jonas
Copy link
Contributor Author

jonas commented Nov 16, 2016

Did one last pass


```
curl https://financialcryptography.com # uses cacert.org as a CA
```
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ssl

Syntax highlighting thinks that // is a start of a comment. Can we adjust that by giving a hint after ```?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I marked this as sh to fix in jonas/ssl-config@f650944

not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
```
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here as well text after ' is highlighted differently.

ssl_test

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've opened lightbend/paradox#64 to fix this


Play comes with `play.api.test.WsTestClient`, which provides two
methods, `wsCall` and `wsUrl`. It can be helpful to use
`PlaySpecification` and `in new WithApplication`
Copy link

@2m 2m Nov 21, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Paradox comes with quite a convenient way of linking to external scaladoc. It would be nice to go throught this doc and add the links to external APIs.

play_api

Created a ticket for it #52

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, right now I don't think the scaladocs are published.

Copy link

@2m 2m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me. Thanks @jonas for putting the resulting HTML to a GitHub pages. This really makes it so easier to review and give meaningful comments.

I have thought about but not figured out completely how to build and host the docs somewhere for every PR during review. So you (or any other contributor) do not have to do it manually.

Some CI services provide build artifact archiving for PRs, but I was unable to find anything that suited HTML pages.

@jonas
Copy link
Contributor Author

jonas commented Nov 21, 2016

I don't know what limitations GitHub puts on their pages, but one idea would be to have a separate docs-validation repo or organization and push generated docs to its GitHub pages branch using the PR and/or Travis build ID as the path.

@ktoso
Copy link
Contributor

ktoso commented Dec 9, 2016

What's missing here to make this happen; the release process I guess?

// @2m

@2m
Copy link

2m commented Dec 9, 2016

I think we can merge this one.

The release process can be adjusted in a separate PR.

@ktoso
Copy link
Contributor

ktoso commented Dec 9, 2016

Boom, thanks

@ktoso ktoso merged commit cbf2cc5 into lightbend:master Dec 9, 2016
@ktoso
Copy link
Contributor

ktoso commented Dec 9, 2016

Kudos guys for migrating this!

@jonas jonas deleted the paradox branch December 9, 2016 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants