Remote repository and workspace structure
Jump to navigation
Jump to search
Repository Design (Forgejo)
- One organization per stack
Core Stacks
Izara Core - Libraries
- npm modules that can be used by any web service
- one project per subject or grouping of functions
Izara Core - xxxx
- Any stacks that can be used by multiple web services prefixed by Izara Core
- eg: Media
Izara Frontend - Core
- Group all frontends for to core services in this workspace
- Separate projects for each stack
- Izara Frontends - Core project is for foundation microfrontends like rootConfig and auth
Izara Frontend - xxxx
- can split groupings of frontends into workspaces
- eg all Market frontends are in Izara Frontend - Market, one project per stack
Izara xxx - yyy
- Each stack has its own workspace
- prefixed by the web service's name, then the stack, eg: Izara Market - Products
Developers
- When working on a repository developer creates a fork with the same name suffixed with their name in brackets
- If multiple developers working on the same repositories, only one person forks and names that repository, others fork/PR or push to developers fork