Resolving Typesense Errors in Docusaurus Site
TLDR Kevin encounters problems with typesense on their Docusaurus site. Jason assists with variable and port number issues, but scrappy limitations lead to unresolved troubleshooting.
Jun 30, 2022 (18 months ago)
You want to wait for it to fully complete before trying to search
Jul 01, 2022 (18 months ago)
Jul 04, 2022 (18 months ago)
Jul 05, 2022 (18 months ago)
Jul 06, 2022 (18 months ago)
WARNING:py.warnings:/root/.local/share/virtualenvs/root-BuDEOXnJ/lib/python3.6/ site-packages/scrapy/spidermiddlewares/offsite.py:69: PortWarning: allowed_domains accepts only domains without ports. Ignoring entry host.docker.internal:3000 in allowed_domains. warnings.warn(message, PortWarning)
The file that's throwing that exception is inside the scrapy package. I also searched their source code for that error message, and confirmed that the error is coming from within scrappy.
re: workaround, the IP Tables based approach mentioned in the Github issue shared seems to work.
Jul 07, 2022 (18 months ago)
DEBUG:scrapy.core.engine:Crawled (404) <GET <https://www.algotrader.com/docs/virtual_spot_positions>> (referer: <http://host.docker.internal:3000/sitemap.xml>)
virtual_spot_positionswhich is the name of a page in the docusaurus site. Unfortunately, it subsitutes the IP address implied by
host.docker.interalwith the URL of the organization. And it can't find
virtual_spot_positionsof course. Arrgh. Redirecting the port does solve one problem but led in this case to another. I will attempt to duplicate the environment that was described in the GitHub posting. In the case where I encountered this problem, the docusaurus site was running in Windows whereas typesense was running in docker run on WSL Ubuntu on the same physical machine. In the configuration where port redirection succeeded, the docusaurus ssite was running on ubuntu. This might explain why it works in one situation but not another.
Jul 08, 2022 (18 months ago)
Indexed 3015 threads (79% resolved)
Trouble with DocSearch Scraper and Pipenv Across Multiple OSs
James ran into errors when trying to build Typesense DocSearch Scraper from scratch, and believes it’s because of a bad Pipfile.lock. Jason attempted to replicate the error, and spent hours trying to isolate the issue but ultimately fixed the problem and copied his bash history for future reference. The conversation touches briefly on the subject of using a virtual machine for testing.
Configuring Docusaurus and Typesense for a Documentation Site
Apoorv had trouble adding search functionality to a Docusaurus documentation website with Typesense. Jason worked through several troubleshooting steps, identified issues with Apoorv's setup, and ultimately provided solutions that successfully implemented the search bar function.
Troubleshooting Typesense Docsearch Scraper Setup Issue
Vinicius experienced issues setting up typesense-docsearch-scraper locally. Jason identified a misconfiguration with the Typesense server after checking the .env file, and recommended using ngrok or port forwarding for development purposes. Vinicius successfully resolved the issue with port forwarding.
Solving Typesense Docsearch Scraper Issues
Sandeep was having issues with Typesense's docsearch scraper and getting fewer results than with Algolia's scraper. Jason helped by sharing the query they use and advised checking the running version of the scraper. The issue was resolved when Sandeep ran the non-base regular docker image.
Troubleshooting TypeSense Errors with Docusaurus Website
James experienced errors integrating TypeSense with a Docusaurus website. Kishore Nallan and Jason provided support, resolving issues with SSL, quoting in the ini file, and a missing index.