Skip to content

Proposal: copy attachments #232

Description

@robtsah

I'm using slack-export-viewer on a remote server because my Slack export archive is too large to process locally.

I run the slack-export-viewer command to generate the output directory, which I serve as a static website using Nginx.

Problem:
Files and attachments (such as images, uploaded documents, etc.) are not copied into the output directory during export. As a result, links in the generated HTML point to files that do not exist locally, making attachments inaccessible when browsing the exported site via Nginx.

Expected behavior:
Attachments referenced in the exported conversations should be present in the output directory and accessible from the static site.

I get this:

Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions