Backup/restore cycle

There are three levels of data assets, and each of them has a tool dedicated to manage the backup/restore cycle.

File Cycle

The file cycle will be managed by Git or some file-based version control system. This tool will manage all file-based artifacts related to PKC. Within the PKC DevOps system, there are three kind of file objects:

PKC Deployment

The PKC deployment project is the first project to be developed and deployed to users. It is stored as a Git-based project directory, and use git clone http://github.com/xlp0/PKC as a handle to publish its latest results. Ideally, this project should try to maintain backward compatibility, or reveal changes when loading new content.

PKC Docker Images

All PKC-related docker images will also be managed in various file-based directory structures, and will be published at http://github.com/xlp0/ website. These projects will provide build processes to create relevant Docker Images.

PKC Intial Data Content

One feature of PKC is that it bundles many pre-determined configuration information in a *.tar.gz or *.zip file, so that it can be quickly loaded without requiring users to tediously filling up all the relevant configuration data. It also provides a convenient mechanism to package up the entire data set of a PKC instance. Packaging up all content of a PKC in a *.tar.gz or *.zip file allows people to migrate a set of computing services, along with all the data set in a rather consistent manner. Therefore, serving as a NFT or Non-Fungible Token in a world that is infested with networked computers.