create a remote backend store from which you can safe push and safe pull your encrypted database assets.

provision a github repository backend

We want to provision (create) the safe's remote (github) backend so that we can access it from different machines. This is how we provision a Github remote backend do it.

safe remote –provision

Before you use safe remote to provision a github git repository backend for your crypts ensure that

Below is the sequence of commands leading up to safe remote --provision

safe init db.admin
safe login db.admin
safe open remote.backend github
safe put @github.token 43210fedcba43210fedcba43210fedcba43210fedcba
safe configure backend db.admin/remote.backend/github
safe remote --provision

focus | safe put @github.token

@todo - we need to refactor out this business of configuring the backend. This should be done automagically by the remote commaand expecting to be at the correct book/chapter/verse

safe knows how to talk to the Github Rest API as long as you provide a github access token. Visit how to acquire a Github access token.

safe configure @github.token

The safe configure command tell's safe which book, chapter and verse (in our case db.admin/remote.backend/github) that contains the backend repository access properties.

safe remote –provision

A number of setup tasks are executed when you ask that the backend repository be created.

Now you are ready to push and pull.

Visit the safe push and safe pull documentation to discover howto use your safe database on as many machines as you need.

where is the safe database?

A safe database is always encrypted at rest and consiss of just 3 simple parts