Scheduling email and FTP in Superset 0.33 version on RHEL Linux environment-Not working
See original GitHub issueHi,
I am trying to configure Scheduling and FTP in Superset 0.33 version on Linux env. I have used Celery, Celery beat , Redis, geckodriver, headless firefox, Nginx, Gunicorn but not able to receive an email not even a test mail which is part of dryrun.
I would like to know if scheduling works on Linux environment and what specific configurations needs to done for Linux env.
Environment
- superset version: 0.33
- python version: `3.7
- Linux Environment
-Thank you, Nithya A
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Scheduling email and FTP in Superset 0.33 version on RHEL ...
Hi, I am trying to configure Scheduling and FTP in Superset 0.33 version on Linux env. I have used Celery, Celery beat ,...
Read more >Red Hat Enterprise Linux-5-5.9 Technical Notes-en-US - Scribd
The Red Hat Enterprise Linux 5.9 Technical Notes list and document the changes ... a code in this version does not work properly...
Read more >https://www.magnicomp.com/sysinfo/examples/redhat-...
Entry Type : pkg Name : ftp Version : 0.17 Revision : 7 Category : Applications/Internet Requires OS Name : linux Requires Architecture:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Issue-Label Bot is automatically applying the label
#question
to this issue, with a confidence of 0.75. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.
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. For admin, please label this issue
.pinned
to prevent stale bot from closing the issue.