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

Create docs_config.js on publish #9

Merged
merged 11 commits into from
Apr 3, 2019
Merged

Create docs_config.js on publish #9

merged 11 commits into from
Apr 3, 2019

Conversation

wojtekmach
Copy link
Member

No description provided.

end

# TODO: don't hardcode https://hexdocs.pm, it should work on staging.hexdocs.pm too!
defp hexdocs_url("hexpm", package, version), do: "https://hexdocs.pm/#{package}/#{version}"
Copy link
Member Author

Choose a reason for hiding this comment

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

@ericmj do we already have the host somewhere or we'd need a new env variable for it? Or is there a simpler way?

Copy link
Member Author

Choose a reason for hiding this comment

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

I got it, I think we can use HEXDOCS_DOCS_PUBLIC_BUCKET.

@wojtekmach wojtekmach marked this pull request as ready for review April 2, 2019 18:41
@wojtekmach
Copy link
Member Author

The only thing left here is I can't figure out why cache isn't busted when we publish docs for a release that's not gonna be the latest release. I also need to set up the redirect on vastly which will be a PR in another repo.

[docs_config_js_upload_file] =
list_upload_files(repository, package, version, [docs_config_js], :unversioned)

upload_new_files([docs_config_js_upload_file])
Copy link
Member

Choose a reason for hiding this comment

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

Include this file in paths above. Should be a little less duplicate code and we can parallelize the upload.

lib/hexdocs/bucket.ex Outdated Show resolved Hide resolved
@ericmj
Copy link
Member

ericmj commented Apr 2, 2019

The only thing left here is I can't figure out why cache isn't busted when we publish docs for a release that's not gonna be the latest release.

Is this broken currently? I would think it would have been reported already.

ericmj and others added 2 commits April 2, 2019 20:54
Co-Authored-By: wojtekmach <wojtekmach@users.noreply.github.com>
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

2 participants