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

Improve documentation regarding Scheduling and Emailing Reports #11235

Closed
VMois opened this issue Oct 12, 2020 · 9 comments
Closed

Improve documentation regarding Scheduling and Emailing Reports #11235

VMois opened this issue Oct 12, 2020 · 9 comments
Labels
enhancement:request Enhancement request submitted by anyone from the community

Comments

@VMois
Copy link

VMois commented Oct 12, 2020

Is your feature request related to a problem? Please describe.

  • no example/steps (or link to another doc page) regarding setting up a Celery worker for email scheduling
  • missing information about naming in EMAIL_REPORTS_WEBDRIVER. Docs suggest geckodriver and chromedriver, but in reality, it is firefox and chrome

Describe the solution you'd like

  • add example regarding EMAIL_REPORTS_WEBDRIVER
  • step-by-step instruction including setting up a Celery worker (or linking existing documentation of exists)

Describe alternatives you've considered
No alternatives

Additional context
Link to existing docs - https://superset.apache.org/docs/installation/email-reports

@VMois VMois added the enhancement:request Enhancement request submitted by anyone from the community label Oct 12, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label #enhancement to this issue, with a confidence of 0.97. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@DRavikanth
Copy link

I agree with this. Documentation is very poor and no clear instructions on how to set things up for production environments. I am trying to make Superset work with email scheduling including Celery and it's been 3 days and my struggle continues. I am making progress but I have to debug each and every minute detail. I am very disappointed with not even finding an official architectural image in the documentation. :(

@VMois
Copy link
Author

VMois commented Oct 31, 2020

From my side, I managed it with some struggle. Use Redis, do not try filesystem as a backend. This is the article I was using - https://medium.com/@nileshxbhosale/apache-superset-a-cost-effective-alternative-to-quick-sight-for-data-lake-668868fe51c7 (+ docs).

@DRavikanth
Copy link

#11507

@VMois, running into this problem. Any pointers?

@VMois
Copy link
Author

VMois commented Nov 3, 2020

@DRavikanth if you are using Docker Compose add the following to your superset image:

superset:
    shm_size: '2gb'  # fix for gecko driver failure
    # ...

You can find the same in the article I shared with you.

@DRavikanth
Copy link

@VMois, Thanks for the pointer. I missed that totally, let me try that and keep posted here.

@VMois
Copy link
Author

VMois commented Nov 3, 2020

@DRavikanth, pls, create a separate issue for your problem. Describe your setup, etc. This is an issue related to improving docs.

Regarding your problem, it is a different error compared to what you had. Good sign. Check if you have the latest stable version of the geckodriver, I have 0.27.0. Other than that, I did everything exactly like in the article, so I cannot help you a lot as I don't know the full setup.

@DRavikanth
Copy link

@VMois, makes sense.

@octaviancorlade
Copy link
Contributor

The documentation for these was introduced in #13104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement:request Enhancement request submitted by anyone from the community
Projects
None yet
Development

No branches or pull requests

4 participants