Arquivando os dados públicos de um fórum

Suporte
1

Gostaria de consultar sobre quais opções existem para o arquivamento público de um fórum.

Recentemente migramos do phpBB e anteriormente tínhamos um script que arquivava as postagens públicas em um arquivo de texto. Existem opções assim para o Discourse? Temos cerca de 30 categorias públicas que precisariam ser arquivadas. O nome de usuário/nome de exibição de cada autor precisaria ser incluído, mas não o e-mail, endereços IP ou qualquer outro dado privado. SQL para que os dados pudessem ser processados como o SEDE da Stack Exchange provavelmente seria o mais útil.

Certo, então eu criei isso. Parece funcionar bem para mim, embora precise verificar se estou filtrando corretamente todas as postagens ocultas. E algumas das colunas provavelmente não são realmente tão úteis.

Isso pode ser usado a partir de um cronjob, mas o usuário precisará ser adicionado ao grupo docker. Adicionei uma etapa após o dump para copiar o arquivo via scp para o servidor de arquivamento, mas você poderia fazer praticamente qualquer outra coisa com ele também.

#!/bin/bash

# Arquivar dados públicos do fórum

EXEC="docker exec -i -u postgres -w /var/www/discourse app"

# Executar comandos para construir as tabelas exportadas
$EXEC psql discourse << EOF

SET client_min_messages TO warning;

DROP TABLE IF EXISTS users_export;
CREATE TABLE users_export AS
  SELECT id, username, created_at, name
  FROM users
  WHERE staged = false;

DROP TABLE IF EXISTS categories_export;
CREATE TABLE categories_export AS
  SELECT id, name, slug, parent_category_id
  FROM categories 
  WHERE read_restricted = false;

DROP TABLE IF EXISTS topics_export;
CREATE TABLE topics_export AS
  SELECT t.id, t.title, t.last_posted_at, t.created_at, t.updated_at,
    t.views, t.posts_count, t.user_id, t.last_post_user_id, t.reply_count,
    t.category_id, t.closed, t.slug
  FROM topics AS t
  INNER JOIN categories_export AS c ON t.category_id = c.id
  WHERE t.deleted_at is NULL AND t.archived = false;

DROP TABLE IF EXISTS posts_export;
CREATE TABLE posts_export AS
  SELECT p.id, p.user_id, p.topic_id, p.raw, p.created_at, p.updated_at,
    p.reply_to_post_number, p.reply_count, p.quote_count, p.like_count
  FROM posts AS p
  INNER JOIN topics_export AS t ON p.topic_id = t.id
  WHERE p.post_type = 1 AND p.deleted_at is NULL AND p.hidden = false;

EOF

# Exportar dados
echo Exportando dados...
$EXEC pg_dump discourse -t users_export -t categories_export -t topics_export -t posts_export > forum-archive.sql

# Limpeza
$EXEC psql discourse << EOF

SET client_min_messages TO warning;

DROP TABLE IF EXISTS users_export;
DROP TABLE IF EXISTS categories_export;
DROP TABLE IF EXISTS topics_export;
DROP TABLE IF EXISTS posts_export;

EOF
1 curtida
2

This is something I am interested in, there are a few topics touching on this already.

You can get fairly close by crawling with a webcrawler user agent, and saving the results as static HTML files. There are tools that do this, as covered in some existing topics.

Might be something we could run an external project for @sam to make a “pretty” version of that.

4 curtidas
3

Is the plan to put the site in “cold public storage” for a time and perhaps re-start the forum later? If that’s the case, then just saving the backup (rather than wanting to re-import the data back to Discourse later) solves that problem and would allow people to be re-connected with their accounts.

Or, do you want to periodically push off part of the live forum to another static site?

You want just the topics and not user pages? Are internal links important? Is a single text file per topic what you’re looking for, or would you prefer HTML that preserved at least some formatting and images and such?

3 curtidas
4

It can’t be a full normal backup because that has lots of private information.

Previously, before we migrated, the archiving was partly for data preservation purposes. But now we have both Linode and S3 backups, so that’s not really necessary. Now an archive that would let you explore and process the data would be useful. If you’re familiar with Stack Exchange’s SEDE, that’s the sort of thing I’d like to enable. So a sanitised SQL dump would be best I think.

I’m going to install the data explorer plugin, then have a look at what columns there actually are. I might be able to figure out the sql commands I need myself.

Sorry to use you all as programming rubber ducks :wink:

4 curtidas