¶ Git
TODO
¶ Project Settings
TODO
¶ Database Schema
TODO
¶ Platform Roles
| Role | System Entity | Cardinality | Description / Capabilities |
| administrator | System | -- | Full system admin. Manages the entire platform. |
| super_content_manager | System / Global | -- | Support/help role. Can alter all courses, skills, job roles and general content; |
| user | Global | -- | Basic logged-in user. Baseline authenticated account. |
| learner | Global | -- | Attends courses, gains badges, generates learning paths, sees microcredentials and progress. Can be added to a corporation (by acceptance or own request). |
| corporation_owner | Corporation | One per corporation | Creates and manages admins; full control over the corporation; can delete it. Can do everything as admin can. |
| corporation_admin | Corporation | Many per corporation | Created by the owner. Manages all corporation members and the corporation's views/learners. |
| corporation_member | Corporation | Many per corporation | Managed by admins. CRUD only selected/assigned views; CRUD learners to those views. |
| provider_owner | Provider | One per provider | Creates the provider and its admins; full control over the provider; can delete it. A provider may be a physical person or a company. |
| provider_admin | Provider | Many per provider | Created by the owner. Manages all provider members. |
| provider_member | Provider | Many per provider | Managed by admins. Creates courses and manages courses they created. |
¶ OLD
Deployment (production)
WHEN YES (recommended)
- Mon–Thu morning / early afternoon (ideally e.g. 8:00–10:00 AM).
- When there are no critical activities within the next X hours (presentation, external demo, monthly close, etc.).
- When at least the key checks are completed: tests have passed.
WHEN NO (not recommended / should be blocked)
- Late afternoon (especially Friday afternoon).
- Right before a meeting / presentation.
- When there’s no time buffer for fixes.
- When the change is large / risky without the ability to roll back quickly (DB migrations without backward compatibility, big refactors without feature flags).
- When the key person isn’t available (the one who knows the change and can fix it quickly, or is needed to resolve other technical issues).
NOTES
- Before deploying to production, DO NOT FORGET to create a backup branch for prod bra.
- Prefer smaller, more frequent deployments over large bundled releases.
Database schema
This section is a technical documentation of the database schema with loose guidelines.
The goal is not to describe all attributes of all tables, but to record aspects of the schema that may not be immediately clear or were created with specific purposes.
DRIVES_SCK
- category(varchar 75) - for values ‘professional’, ‘general’ and ‘soft’
DRIVES_Training
- cost (long) - course price in cents
DRIVES_LearningPath
- pathType (string) - strictly limited to the values "PREDEFINED", "GENERATED", or "CUSTOM"
- externalGuarantor (string) – used for the guarantor’s name if the guarantor is not a user on the platform. If a link exists between LP and User_ (LPathToPerson with assignmentType eq "GUARANTEED"), that link takes precedence
Git
- Project GIT Repository: https://git.scoveco.cz/drives/platform
- Trunk based development process.
- Git Approach
- Branches SkillsHub
| master | Inactive Production branch | |
| SKILLS-HUB-prod | Production branch | https://skills-framework.eu/home |
| testing | Development branch | https://drives-compass.vsb.cz/ |
| feature- | Feature branch |
- Branches Dovednosti MSK
| TRAUTOM-prod | Production branch | https://dovednosti-msk.cz/home |
| TRAUTOM-test | Development branch | Staging server: https://drives-compass.vsb.cz/web/dovednosti-msk Prod server testing subsite: https://dovednosti-msk.cz/en/web/dovednosti-testing |
| feature-msk- | Feature branch |
Project setting up and DEV Environment
- Guidelines file: ASA - DEV Project Setting up.docx (IN PROGRESS)