Difference between revisions of "Close Cycle Data Management"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
#For behavioral data analytics: Get [[Matomo]] to work for all services. | #For behavioral data analytics: Get [[Matomo]] to work for all services. | ||
#For authentication and authorization: Get [[Keycloak]] to work with all these services. | #For authentication and authorization: Get [[Keycloak]] to work with all these services. | ||
#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.
- For time signature management, use Blockchain.
- 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 behavioral data analytics: Get Matomo to work for all services.
- For authentication and authorization: Get Keycloak to work with all these services.
- 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 Browser-based development: All relevant source code should be editable by VS-Code server.