Advice on archiving a site

[jbrains (J. B. Rainsberger)]

@NateDhaliwal

Perhaps wayback machine?

I find this idea very interesting and creative, but I think I prefer to have the option to browse the comments offline easily.

@twofoursixeight

Would this work for archiving your site?

For what it’s worth, I’ve written a minimum viable Python script that performs simple backup of post content using the API: GitHub - jamesob/discourse-archive: Provides a simple archive of Discourse content It’s pretty barebones, but should give someone a rough idea of how to generate a suitbable-for-public archive.

Might not be the best option, but this older discussion seems like a useful start.

Maybe so. Thank you for the idea. I believe I used this to archive a community Discourse that I used as part of a training course. I then distributed the archive to the participants for their reference.

@rishabh

This reminds me of Mirroring a read-only mailing list in Discourse, but without the mailing list part.

@jbrains

I infer that I want to archive the Discourse site, so that I can then serve it locally and browse it and grab content in an “as I need it” fashion to rewrite or edit a post.

Maybe running the site in read-only mode or development mode on your network is the way to go?

Also if you only need to sift through post content and don’t need the Discourse UI, a simple Discourse Data Explorer query can let you download a csv/json file with the data that you can use other applications to search.

Aha! This is exactly the kind of thing that I was looking for. Thank you for pointing me to it. I’ll take a look.