Difference between revisions of "Close Cycle Data Management"
Jump to navigation
Jump to search
(Created page with "This is about showing that data assets in PKC are self-referenced. #Get Moodle and Gitea/Gitlab to be insertable or removeable from the functional list of PKC. #Get Matomo to...") |
|||
| 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. | ||
#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. | ||
#Get Matomo to work for all services. | #For behavioral data analytics: Get Matomo to work for all services. | ||
#Get Keycloak to work with all these services. | #For authentication and authorization: Get Keycloak to work with all these services. | ||
# Use Gitea or Gitlab services in PKC to host the source that we are building, with Nginx. | #For source code control: Use Gitea or Gitlab services in PKC to host the source that we are building, with Nginx. | ||
# | #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:12, 31 May 2022
This is about showing that data assets in PKC are self-referenced.
- 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, with Nginx.
- For Browser-based development: All relevant source code should be editable by VS-Code server.