Difference between revisions of "Close Cycle Data Management"

From PKC
Jump to navigation Jump to search
Line 7: Line 7:
#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 page provision: 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]].


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

Revision as of 06:16, 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 work for all services.
  5. For authentication and authorization: Get Keycloak to work with all these services.
  6. For source code control: Use Gitea or Gitlab services in PKC to host the source that we are building
  7. For static page provision: Always use Nginx.
  8. For Browser-based development: All relevant source code should be editable by VS-Code server.