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

Publish PDF to S3 if available #344

Merged
merged 1 commit into from Apr 16, 2015
Merged

Publish PDF to S3 if available #344

merged 1 commit into from Apr 16, 2015

Conversation

spohnan
Copy link
Contributor

@spohnan spohnan commented Apr 16, 2015

  • Extract documentation.pdf from site archive within our tarball distribution so it's more obvious
  • Copy documentation.pdf to S3 if aws command is availble
  • Link to pdf from our docs
  • I added a docs directory to our geowave S3 bucket and added a policy that makes everything public
  • Worked around an Asciidoc formatting bug where the end of one section uses a formatting construct like a list or a table and it does not correctly recognize the next section marker. I changed a bullet list into two paragraphs

@coveralls
Copy link

Coverage Status

Coverage remained the same at 57.18% when pulling eab47f4 on publish-pdf-doc into 50f31b5 on master.

rwgdrummer added a commit that referenced this pull request Apr 16, 2015
@rwgdrummer rwgdrummer merged commit f4de1b8 into master Apr 16, 2015
@spohnan spohnan deleted the publish-pdf-doc branch April 16, 2015 18:34
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