Difference between revisions of "PKC DevOps/Input"

From PKC
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
#Specify a [[PKC namespace]]
#Specify a [[PKC namespace]]
#[[PKC Dependent Source Code Repositories]]
#[[PKC Dependent Data Repositories]]
#Development Human Resources
## [[PKC Dependent Source Code Repositories]]
#Initial User Group
#[[Human Resources for PKC Development]]
##[[PKC User Community]]
#[[PKC]] Design Orientation and Design Pattern Guidelines
#[[PKC]] Design Orientation and Design Pattern Guidelines
##Written in [[PKC]] and deployed as the base [[PKC mountPoint]] tar ball.
##Written in [[PKC]] and deployed as the base [[PKC mountPoint]] tar ball.
#Dockerhub.io
#Standardised Mount Directory for Extension Development
#Standardised Mount Directory for Extension Development
##MountPoint Hierarchy Rules
##MountPoint Hierarchy Rules
Line 13: Line 13:
##Set [[Medik default values]]
##Set [[Medik default values]]
##Evolve CSS/Common.js
##Evolve CSS/Common.js
#Default RBAC
#Default [[PKC RBAC Configurations]]
##LocalSetting.php options
##LocalSetting.php options
##Define standard User Types
##Define standard User Types
Line 19: Line 19:
<noinclude>
<noinclude>
==Related Pages==
==Related Pages==
*[[has LogicModel::Task/PKC DevOps]]
*[[has LogicModel::PKC DevOps]]
</noinclude>
</noinclude>

Latest revision as of 03:57, 18 August 2021

  1. Specify a PKC namespace
  2. PKC Dependent Data Repositories
    1. PKC Dependent Source Code Repositories
  3. Human Resources for PKC Development
    1. PKC User Community
  4. PKC Design Orientation and Design Pattern Guidelines
    1. Written in PKC and deployed as the base PKC mountPoint tar ball.
  5. Standardised Mount Directory for Extension Development
    1. MountPoint Hierarchy Rules
    2. Data verification with Data Accounting Extension
  6. UI Specification
    1. Load skins/Medik
    2. Set Medik default values
    3. Evolve CSS/Common.js
  7. Default PKC RBAC Configurations
    1. LocalSetting.php options
    2. Define standard User Types
    3. Provide standard procedure for Admin right access

Related Pages