Difference between revisions of "Close Cycle Data Management"

From PKC
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
This is about showing that data assets in PKC are self-referenced.
This is about showing that data assets in PKC are self-referenced.
#For time signature management, use Blockchain.
#For time signature management, use [[Blockchain]].
#For categorizing and managing namespaces, use MediaWiki
#For categorizing and managing namespaces, use MediaWiki
#For learning management system features, Get Moodle and Gitea/Gitlab to be insertable or removeable from the functional list of PKC.
#For learning management system features, Get [[Moodle]] and Gitea/Gitlab to be insertable or removeable from the functional list of [[PKC]].
#For behavioral data analytics: Get Matomo to work for all services.
#For behavioral data analytics: Get [[Matomo]] to track page visitation statistics for all services.
#For authentication and authorization: Get Keycloak to work with all these services.
#For authentication and authorization: Get [[Keycloak]] to provide authentication and authorization all other applications.
#For source code control: Use Gitea or Gitlab services in PKC to host the source that we are building
#For source code control: Use [[Gitea]] or [[Gitlab]] services in [[PKC]] to host the source that we are building
#For static page provision: Always use Nginx.
#For static file download: Always use [[Nginx]].
#For Browser-based development: All relevant source code should be editable by VS-Code server.
#For Browser-based development: All relevant source code should be editable by [[VS-Code server]].
#For Browser-based testing: Always use [[Selenium]].


[[Category:PKC Workflow]]
[[Category:PKC Workflow]]

Latest revision as of 06:20, 31 May 2022

This is about showing that data assets in PKC are self-referenced.

  1. For time signature management, use Blockchain.
  2. For categorizing and managing namespaces, use MediaWiki
  3. For learning management system features, Get Moodle and Gitea/Gitlab to be insertable or removeable from the functional list of PKC.
  4. For behavioral data analytics: Get Matomo to track page visitation statistics for all services.
  5. For authentication and authorization: Get Keycloak to provide authentication and authorization all other applications.
  6. For source code control: Use Gitea or Gitlab services in PKC to host the source that we are building
  7. For static file download: Always use Nginx.
  8. For Browser-based development: All relevant source code should be editable by VS-Code server.
  9. For Browser-based testing: Always use Selenium.