I did a backup of my site before I upgraded to the latest version of the discourse however I can’t even access my site any more even though the upgrade appears to be successful as no error is displayed. Is there anyway that I can restore my site from the backup that I created earlier from terminal…

[imagen] Ankhamax: Is it possible? Yes. [imagen] Ankhamax: If yes, where do discourse save or store the backups that I executed from the admin panel? They’re stored in public/backups/default/. [imagen] Ankhamax: Is there any guide on how to restore the site from backup? Just r…

This seems like a handy thing to be able to do since if you screw up configuring SSO you can’t get back into your site. So, script/discourse restore fails because thor isn’t installed. gem install thor fixes that, but then I’m still denied because: URGENT: FATAL: Peer authentication failed for…

[imagen] pfaffman: since if you screw up configuring SSO you can’t get back into your site. There’s a way to log in: Visit /users/admin-login, which can be used to log in via email :slight_smile:

It worked for me by first getting into the app ./launcher enter app then discourse enable_restore discourse restore <filename.of.the.backup.tar.gz> discourse disable_restore Using the script/discourse didn’t work

restoring from a app.yml and an external tar.gz file was mixing up some of the items I found along this thread: TARBALL_PATH=$(ls local/backups/-*.tar.gz | tail -n 1) TARBALL_NAME=$(basename ${TARBALL_PATH}) cat ${TARBALL_PATH} | docker exec -i app sh -c "cat - > /var/www/discourse/public/backups/d…

Rather than try to restore from app.yml it’s much easier to just ./launcher enter app and restore it from the command line.

The goal was to automate it without any entering container with the launcher. Imagine your instance got lost for any reason. The only files you stored in git was your containers/app.yml and luckily you have a daily tarball backup.

You can also do it directly to Postgres: dropdb dbname createdb dbname gunzip -c filename.gz | psql dbname

discourse is script/discourse – executed via bundle exec and with rails_env=production. Look at /usr/local/bin/discourse. Running bundle exec script/discourse takes care of the thor mismatched gem version, too. Or just using the discourse convenience script.

Is there any way to restore your site from backup in the terminal?

Soporte

gerhard (Gerhard Schlager) 14 Agosto, 2020 10:05 16

No puedes. Necesitas copiar el archivo de respaldo en el directorio correcto. Sigue las instrucciones en Restore a backup from the command line si deseas restaurar desde la línea de comandos.

Tema		Respuestas	Vistas
Restore a backup from the command line Self-Hosting how-to	18	22130	18 Mayo 2025
Data Backup Self-hosting	5	1760	10 Diciembre 2023
How to backup Docker discourse from command-line before rebuilding broken Discourse? Support	12	4077	23 Mayo 2019
How to restore backup tar.gz file from console command? Support	8	3603	8 Enero 2018
Any other way to take backup and restore? Support	2	3070	23 Junio 2019

Is there any way to restore your site from backup in the terminal?

Temas relacionados