Tirsvad
9cca29579f
TOKEN_FOR_GITEA_WIKI is an optional key, checked and masked but never used or asked for, so one .env can serve the wiki publishing too. GITHUB_PAT and GITHUB_USER are documented as required only when GitHub is chosen. The how-to for creating the access tokens moves from howto/ to the wiki as AccessTokens in English, Danish and Bahasa Malaysia, with its pictures in wiki/img/. README, Home and the sidebar link to it. Adds MIL-010 with its review RC-033 and the matching plan, user story and traceability rows. Task: MIL-010#1 Task: MIL-010#2 Task: MIL-010#3 Closes #83 Closes #84 Closes #85
1.3 KiB
1.3 KiB
English | Dansk | Bahasa Melayu
Repo Foundry
Repo Foundry (src/create-project.sh) sets up a new project in one run:
- a Gitea repository, the source of truth;
- optionally an empty GitHub repository that receives everything through a push mirror from Gitea;
- a local project with one credential-free remote,
origin, and the SQA-QC-Framework as a git submodule, with its skills, git hooks and templates installed.
It is a Bash script. It shows a plan first and creates nothing until you pass --apply and answer yes.
Pages
| Page | What it covers |
|---|---|
| Getting started | Requirements, install and the first run |
| SSH and tokens | SSH access to Gitea and the two access tokens |
| Access tokens | Create the access tokens, step by step with pictures |
| Updating the framework | Keep the framework submodule of a project up to date |
| Troubleshooting | Common failures and what to do |
The full reference (configuration files, security decisions, error handling, known limitations) is the README. Report a problem as an issue.