hfaran
commented
6 years ago Changes to the latter break ability to take downloaded zip (or extracted zip) as input, but if there is interest, I guess the two could be merged together to handle data from either source.
That would be quite nice! I currently don't have time to expend towards that but support any passerbys that would like to pick it up!
I wanted to combine slack-auto-export with this viewer and slack2html to automate the process of exporting a public slack workspace to static html for archival as a git repo, ie. without the need to manually download .zip histories from slack. To do this, I just had to tweak a few lines in both repos. My forks are here, in case they are useful to anyone else - slack-auto-export - given a token and output directory, generates JSON output suitable for my fork of: slack-export-viewer - takes above directory and does what the original viewer does
Changes to the latter break ability to take downloaded zip (or extracted zip) as input, but if there is interest, I guess the two could be merged together to handle data from either source.
This may be of interest/relevant to others with similar needs, eg. #43