Open
Description
Is your feature request related to a problem? Please describe.
The problem is that it's possible to run a server to view the files, but not to deploy a static website (containing just HTML and CSS (and maybe JS) files) which can be viewed without a server, and/or deployed to a simple nginx server.
Describe the solution you'd like
This should convert the entire workspace archive to a locally-browseable static site.
slackdump convert -o bar -output html foo
Describe alternatives you've considered
Do slackdump view foo
and then run a web scraper on that.
Metadata
Metadata
Assignees
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
rusq commentedon Jan 24, 2025
Hey @rudolfbyker thanks for the suggestion.
Have you considered running "slackdump view" behind nginx proxy?
rudolfbyker commentedon Jan 24, 2025
Yes, I have, but I want to have many archives together from various times and from various workspaces, which would mean I must run
slackdump view
for each one of them and create a proxy for each one in nginx. What I would like is to be able to simply copy the new archive's static HTML/CSS/JS files over to the nginx server's docroot, without having to change any settings.rusq commentedon Jan 24, 2025
Fair enough, for multiple websites it would be a pain indeed. Good news is that most of the logic is there to generate HTML from source, but HTML templates would have to be tailored for static representation and the directory structure needs to be thought through.