Core Concepts
Core Concepts explains the model shared by every GoForj App. Start with the question you need to answer rather than reading the section in order.
Choose a Concept
| Question | Read |
|---|---|
| Where does an App begin and how do additional apps differ? | Apps |
| What starts, runs, and shuts down? | App Lifecycle and Runtime Topology |
| How does a constructor become part of the App? | Dependency Injection, then Provider Patterns for conditional or shared construction |
| Why did Wire fail? | Reading Wire Errors |
| How do I add or remove an application resource? | Make Command Reference |
| Which files are regenerated, render-once, or App-owned? | Code Generation |
| Where does a specific service, controller, job, or command get wired? | Wiring Recipes |
| How do names map to packages and generated resources? | Naming Conventions and Named Resources |
| How does runtime configuration select compiled integrations? | Drivers and Adapters |
| How can the same App begin locally and move to shared infrastructure? | Local-First Development |
Related Sections
- Getting Started is the practical entry point.
- Operations applies the runtime model in production.