Skip to content

Update links in FAQ #328

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.

Sign up for GitHub

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

Merged
abitmore merged 1 commit into from
Feb 19, 2025
Merged

Update links in FAQ #328

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/faq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,10 @@ Note: this way has limitation: public nodes doesn't store full account history,
only limited number of entries

* By querying `elasticsearch plugin
<https://dev.bitshares.works/en/master/supports_dev/elastic_search_plugin.html>`_.
<https://docs.bitshares.dev/en/master/supports_dev/elastic_search_plugin.html>`_.
In short, elasticsearch plugin export account history data into elasticsearch
instance, from which it's can be obtained directly or via elasticsearch
wrapper. See `<https://eswrapper.bitshares.eu/apidocs/>`_ to get info on how
wrapper. See `<https://api.bitshares.ws/docs>`_ to get info on how
to query the wrapper. A real-world example of elasticsearch wrapper usage for
obtaining filled orders history is `bitshares-tradehistory-analyzer
<https://github.com/bitfag/bitshares-tradehistory-analyzer>`_
Expand Down
Loading