[GH-ISSUE #168] No crawler options in Settings page #166

New issue

Closed

opened 2026-02-27 15:55:26 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:55:26 +03:00

Owner

Originally created by @svetsch on GitHub (Jun 24, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/168

Hi,

First thanks for your great project, I found it really clear and well structured.

I'm trying to follow the instructions of the page:
https://blog.ambar.cloud/crawling-and-searching-email-inbox-with-ambar/

But with my fresh install, the document processing is working fine, but the settings page only displays the logs and there is no options related to crawlers.

Is there anything that I may have missed ?

Originally created by @svetsch on GitHub (Jun 24, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/168 Hi, First thanks for your great project, I found it really clear and well structured. I'm trying to follow the instructions of the page: https://blog.ambar.cloud/crawling-and-searching-email-inbox-with-ambar/ But with my fresh install, the document processing is working fine, but the settings page only displays the logs and there is no options related to crawlers. Is there anything that I may have missed ?

kerem

2026-02-27 15:55:26 +03:00

closed this issue
added the
help wanted

wontfix
labels

kerem commented

2026-02-27 15:55:27 +03:00

Author

Owner

@sochix commented on GitHub (Jun 28, 2018):

Hi @svetsch
From version 2.0, Ambar supports only local fs crawling. So the article is outdated. Now it's unpublished. Sorry for inconvenience.

@sochix commented on GitHub (Jun 28, 2018): Hi @svetsch From version 2.0, Ambar supports only local fs crawling. So the article is outdated. Now it's unpublished. Sorry for inconvenience.

kerem commented

2026-02-27 15:55:27 +03:00

Author

Owner

@stale[bot] commented on GitHub (Sep 10, 2018):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 10, 2018): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.