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

Upload generated sphinx documentation to S3 #4217

Closed
exalate-issue-sync bot opened this issue May 22, 2023 · 3 comments
Closed

Upload generated sphinx documentation to S3 #4217

exalate-issue-sync bot opened this issue May 22, 2023 · 3 comments
Assignees

Comments

@exalate-issue-sync
Copy link

No description provided.

@exalate-issue-sync
Copy link
Author

Angela Bartz commented: We already have a ProxyPass that redirects Sparkling Water 2.2, 2.1, and 2.0 Scaladocs to /latest-stable. For example:

ProxyPass "/sparkling-water/2.2/latest-stable/" "http://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.2/7/"

Ideally, the HTML output should point to a similar location/path so that there is no need for another ProxyPass statement.

https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.0/22/userguide/index.html#package
https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.1/21/userguide/index.html#package
https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.2/7/userguide/index.html#package

@DinukaH2O
Copy link

JIRA Issue Migration Info

Jira Issue: SW-703
Assignee: Jakub Hava
Reporter: Jakub Hava
State: Resolved
Fix Version: 2.0.23
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#560

@hasithjp
Copy link
Member

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2018-02-02T02:35:44.912-0800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants