-
Notifications
You must be signed in to change notification settings - Fork 776
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
Installing some Dash feeds results in docsets without names #514
Comments
You could utilise a Dash XML feed for sharing your docset, but other than that there's no way to add new docsets to Zeal. I am currently working on adding more sources of docsets, that will allow to resolve #315. For now maybe I should create a wiki page with a list, and point to it from the website... |
Added feed and download, hosted on free-tier Heroku: http://pxdoc.herokuapp.com/, original repo also points there. Observations:
How do I fix the latter? The former is probably some Heroku issue I can live with. |
I completely forgot about this one :( If you are still interested, a quick fix would be renaming feed file to follow |
@k3rni Thanks for providing the Phoenix feed, but it doesn't work anymore ( |
Haven't touched that in a long time. I think the 410 is due to the file disappearing from Heroku itself, but the docs don't build - something must have changed upstream. Will give it a shot. |
Today I noticed that if I add feed using URL |
https://gitlab.com/k3rni/pxdoc is a docset for the Phoenix Framework.
When my PR to add it to Dash was rejected, I learned that Dash already has one, but it works only with Dash's special Hexdocs support, and is thus not available for Zeal.
Currently, the CI process on gitlab builds it, and generates a zipfile with build artifacts, which in turn contains
Phoenix.tgz
, the proper end product.Works fine when unpacked into Zeal's docset directory (or symlinked into, after building from source). How do I proceed with having it added? Where do I host it properly? I see #315 is still not resolved, and Zeal's documentation on that topic is rather scarce.
The text was updated successfully, but these errors were encountered: