Purpose
GitHub is Cloudberrie’s system of record for source code, documentation source, change history, reviews, releases, and deployment integrations. This handbook begins with a brand-new account and ends with a protected, business-owned repository connected to Cloudflare.
Cloudberrie rule: repositories must live inside the business organization. Do not make a founder’s personal namespace the permanent home of company code.
Recommended Cloudberrie Model
| Item | Recommended value |
|---|---|
| Administrative login | accounts@cloudberrie.com using a role-based GitHub user such as cb-engops |
| Organization | cloudberrie-studio or the approved available equivalent |
| Plan | Start with GitHub Free; review Team when advanced organization-wide governance is required |
| Repository visibility | Private by default |
| Default branch | main |
| Authentication | 2FA mandatory; passkeys/security keys preferred where practical |
Implementation Sequence
- Create and secure the administrative GitHub account.
- Create the Cloudberrie organization.
- Configure organization identity, member policies, and base permissions.
- Create teams and assign least-privilege access.
- Create the first repository.
- Install Git locally and push the project.
- Adopt branch, commit, PR, and review standards.
- Protect
mainwith repository rulesets or branch protection. - Enable repository security capabilities available on the selected plan.
- Connect the repository to Cloudflare Pages and verify previews and production deployment.
Cloudberrie Repository Portfolio
| Repository | Purpose |
|---|---|
cb-website | Cloudberrie public website |
cb-manual | Business & Operations Manual |
cb-studio-board | Internal Studio Board application |
cb-eventlumi | EventLumi product |
cb-aifa | AIFA product |
cb-infrastructure | Infrastructure configuration, scripts, safe DNS exports, and deployment utilities |