Difference between revisions of "Backup/restore cycle"
Line 1: | Line 1: | ||
There are three levels of data assets, and each of them has a tool dedicated to manage the 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= | =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]]. | 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 <code>git clone http://github.com/xlp0/PKC</code> 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 <code>http://github.com/xlp0/</code> website. These projects will provide build processes to create relevant Docker Images. | |||
=Service Cycle= | =Service Cycle= | ||
=Page Cycle= | =Page Cycle= |
Revision as of 09:04, 30 August 2021
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.