Move a workspace copies one workspace's books into a single package file, or loads a package file into this server. You reach it from Settings > Local workspace, by choosing Move a workspace. There are three screens: Export to local, Import to cloud, and History.
Where it is switched on
These screens are off unless local workspaces have been switched on in your version of Finocket. Where they are off, each screen says only that local workspaces are not switched on, and nothing here applies. Even where they are on, a server that has not been set up for moving workspaces tells you so: Moving a workspace is not set up on this server.
Export to local
Choose a workspace you own on this server. If you do not own one, the screen says so. Then choose what to export:
- A copy: this workspace stays the live one.
- A backup copy: this also works from a read-only copy.
Choose Preview. The preview reads the workspace and writes nothing. It shows how many rows are in how many tables, the package hash, the file checksum (which differs on every export), the file size, and the key the package is signed with. Then choose Download package, or Save to a folder if your browser can save to a folder. If it cannot, the screen says so and Download is the way.
Before anything is saved the file is checked against what you previewed. If the file did not arrive intact, or the workspace changed after the preview, nothing is saved and you preview again.
The package is a copy. The workspace here stays as it is. Load the package on a server that runs the local workspace: this build cannot open a package inside the browser yet.
Import to cloud
Choose a package file and then Check the package. Checking writes nothing. It tells you whether the signing key matches a key pinned on this server, and how many rows loading would add to this server.
To load it, type the phrase the screen shows for that package, then choose Load the package. Every figure is checked as it loads. If a check fails, the load is refused, and the screen says which of these happened:
- It was refused before anything was written.
- It was refused after rows were written, and those rows were removed again. Any people or workspace record it had to create, and any stored files, are left in place.
- It was refused after it had started writing, and the removal could not be confirmed. Check History before you try again.
A loaded workspace is a read-only copy
After a load, the workspace is a read-only copy until you make it the live one. Do that only once the workspace the package came from is no longer used. Two live copies would each take entries the other never sees. To make it live, confirm that the original is no longer used, type PROMOTE, and choose Make it live.
History
History lists who previewed, exported, loaded or made a workspace live on this server, when, the result, and the hash of the package. An empty list means nothing has been moved yet.
Related
To keep a workspace in a folder or on a drive you choose, see Settings > Local workspace and Offline & sync.