-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export clients & client_trusted_domains #8719
Comments
@cobbspur FYI. This issue will be resolved in Ghost 2.0. We export more data in Ghost. This can be helpful in case we need to use a backup JSON. |
The challenge here is that exporting/importing the trusted domains without the clients doesn't work out of the box, because this table holds a MySQL reference to the clients table and MySQL will complain on import. The connection of clients <-> trusted domains makes it in theory possible that only specific client credentials are tied to a trusted domain. Keep in mind that Ghost requires the client credentials only for password authentication and the public api. If you are talking to the API with a Bearer token, client validation is skipped, because client authentication happened already. Options
|
We will go with this path for now. |
Closing, because we have added an hidden option to export/import more tables. |
The Ghost exporter takes care of excluded tables, see https://github.com/TryGhost/Ghost/blob/lts/core/server/data/export/index.js#L11.
These are: token tables, client and trusted domains.
So if you e.g. export your blog and import the file into your new blog, you have to:
We would like to reconsider not exporting clients and trusted domains.
The text was updated successfully, but these errors were encountered: