Best method to run in production about slack-export-viewer HOT 4 CLOSED

Ahhh okay, thank you I'll give these steps a try!! Yeah I was definitely expecting the localhost launch to "just work" but I see the error of my ways... 😬 Appreciate your help, will let you know how it works out!

from slack-export-viewer.

What steps exactly did you use for setting this up? From what you've mentioned so far, it seems like you're serving content from slack-export-viewer on localhost:5000 on the server and somehow expecting that to hook up automatically to the Apache/mod_wsgi setup you have going. That's not quite going to work. 😛

If you want to use mod_wsgi specifically, you'll need to look into the instructions given here in the Flask docs: http://flask.pocoo.org/docs/0.11/deploying/mod_wsgi/

This will require writing just a few lines of code and knowing where to grab the configured app from. Essentially, you would would have to a different version of main that just did configure_app and returned the Flask app object so that you could use it in the .wsgi file as is described in the Flask documentation linked above.

(This is all from my shallow understanding of how mod_wsgi works because I've never personally used it.)

from slack-export-viewer.

On the other hand...

If you want a simple no-frills solution, just run slack-export-viewer with the flags instead: slack-export-viewer -z <archive_path> --no-browser --ip 0.0.0.0 --port 80 to serve using the built-in werkzeug server directly, without having Apache server in front. Of course, this isn't recommended for production but that really depends on what you're use case is (if it's serving to only a handful of people and you don't care about exposing your Slack archive to the internet at large, this is fine).

from slack-export-viewer.

Another solution: Just use this to just get the HTML itself, and serve that using Apache or nginx directly..

from slack-export-viewer.