Skip to content
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.

Sign up for GitHub

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

docs: add documentation for clone backend #6622

Merged
merged 1 commit into from
Oct 1, 2020
Merged

docs: add documentation for clone backend #6622

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions wiki/content/slash-graphql/admin/clone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
+++
title = "Cloning Backend"
[menu.main]
parent = "slash-graphql-admin"
weight = 7
+++

Cloning a backend allows making a copy of an existing backend. The clone will be created with all the data and schema of the original backend present at the time of cloning. The clone will have its own endpoint and will be independent of the original backend once it is created. Any further changes in either backends will not reflect in the other. Currently, a clone can only be created in the same zone as that of the original backend.

In order to clone your backend, click on the `Clone Backend` button under the [Settings](https://slash.dgraph.io/_/settings) tab in the dashboard's sidebar.

You can also clone using the [Slash GraphQL CLI](https://www.npmjs.com/package/slash-graphql) as a two step process.

1. Create a new backend.
2. Restore data into the new backend from the original backend.

You can also perform the restore operation on an existing backend if you have an unused backend or want to resuse an existing endpoint. But note that the restore operation will drop all the existing data along with schema on the current backedn and replace it with the original backend's data and schema.