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

Clarify DB URI docs, and fix display of --flags that render as -flags in docs (em-dash) #476

Merged
merged 2 commits into from
Dec 15, 2018

Conversation

srowen
Copy link
Contributor

@srowen srowen commented Dec 14, 2018

Description of changeset:

Clarify DB URI docs, and fix display of --flags that render as -flags in docs (em-dash).
I believe this is what #423 was requesting for doc updates. I added a note about sqlite URIs as that worked for us.

Separately I also fixed a small issue, that sphinx seems to collapse -- to an em-dash for flags like --dburi in the docs, which makes them incorrect as -dburi. That also tripped me up for a second.

(There are many instances where code-like text is back-ticked and actually renders as italics, but I didn't bother with those.)

Test Plan:

Manually built docs and verified.

Auto-reviewers: @NiharikaRay @matthewwardrop @earthmancash @danfrankj

@AppVeyorBot
Copy link

port on which the server is running, and the sqlalchemy uri where the database
can be found and/or initiated.
options, such as :code:`--port` and :code:`--dburi` which respectively change the local
port on which the server is running, and the SQLAlchemy URI where the database
Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps instead of your addendum: "and the SQLAlchemy URI of the database to use and/or initialize for the post index (which is distinct from the database, if any, used to store knowledge posts)."

@matthewwardrop
Copy link
Collaborator

matthewwardrop commented Dec 14, 2018

Thanks again for the nit fixes @srowen ! This looks good, modulo a small improvement suggested above. Once that is addressed, I'll pull this in!

Are you using the knowledge repo internally somewhere, or just a good samaritan? :).

@srowen
Copy link
Contributor Author

srowen commented Dec 14, 2018

Sure, I'll update accordingly.

We use it at Databricks to host an exported copy of many notebooks we use to demo to customers. The DB product itself does search on notebooks, but the tagging and upvote and stats feature was valuable enough on top that we run this internally to help discoverability.

@AppVeyorBot
Copy link

@matthewwardrop
Copy link
Collaborator

@srowen Ah! That's interesting. How do you automate the conversion to the Knowledge Repo format?

@srowen
Copy link
Contributor Author

srowen commented Dec 15, 2018

Not much automation really -- Databricks can export notebooks as .ipynb and knowledge repo can import that, and that's more than enough. It can be done via APIs on the command line. Our instance more of a search engine and viewer so if there are any minor issues with markdown in conversion, doesn't matter.

@matthewwardrop
Copy link
Collaborator

@srowen Thanks again for the patch. I'll merge it in now. Thanks for sharing re:the automation process. Always interesting to hear how others are adopting the code.

@matthewwardrop matthewwardrop merged commit 2c8b3b6 into airbnb:master Dec 15, 2018
tanuj208 pushed a commit to ElucidataInc/knowledge-repo that referenced this pull request Jun 6, 2019
… in docs (em-dash) (airbnb#476)

* Clarify DB URI docs, and fix display of --flags that render as -flags in docs (em-dash)

* Update sqlalchemy remark per review
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