FEATURE: Add utilities for backups and remote URLs #32992
+52
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nbianca
commented
Jun 3, 2025
script/discourse
Outdated
| return | ||
| end | ||
|
|
||
| token = EmailBackupToken.set(Discourse.system_user.id) |
There was a problem hiding this comment.
For the case when store is remote (e.g. S3), I can return a presigned URL to avoid dealing with API keys and backup email tokens.
This commit introduces two new features related to the backup and restore system that make use of remote URLs: - `discourse backup_url` generates a URL of a backup file - `discourse restore <backup>` can now accept a URL to a backup file, that is downloaded and then restored These two utilities make it easier to manage backups, especially when trying to move backups between different servers without using an intermediate storage location (download to local machine and then upload to local machine). `discourse backup_url` works only for remote backup stores (S3).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces two new features related to the backup and
restore system that make use of remote URLs:
discourse backup_urlgenerates a URL of a backup filediscourse restore <backup>can now accept a URL to a backup file,that is downloaded and then restored
These two utilities make it easier to manage backups, especially when
trying to move backups between different servers without using an
intermediate storage location (download to local machine and then upload
to local machine).
discourse backup_urlcreates a temporary API key (expires after 1 day)and a "backup token" to access the backup file. The first key is
necessary because only logged in users can access backup files. This
also provides a layer of security because the key is limited to a
specific backup file and token. The second token is necessary to limit
access to the backup file and avoid presigned URLs for longer periods of
time.