How flatcar/nebraska works
Nebraska manages Omaha-protocol update rollouts, with Flatcar-focused update and payload capabilities. Operators configure applications, channels, packages, and instance groups in the web console; instances request updates through Omaha, while the backend serves and records rollout activity. The sampled startup and application-handler code establishes the server, service, and persistence wiring. The README documents broader rollout, statistics, activity, and Flatcar capabilities; unsampled implementation links are omitted or marked unverified.
Main entry points: handler.go HTTP handlers · Main.tsx Console routes · admin Admin service · main.go Application startup
Components 22
Runtime entry
- Application startup
backend/cmd/nebraska/main.go - HTTP server
backend/pkg/server/server.go - HTTP handlers
backend/pkg/handler/handler.go - Application routes
backend/pkg/handler/app.go
Rollout services
- Admin service
backend/pkg/api/admin - Runtime service
backend/pkg/api/runtime/service.go
Persistence
- Application database
backend/pkg/api/internal/dbconn/conn.go - Read queries
backend/pkg/api/internal/dbreads/applications.go
Web console
- Console bootstrap
frontend/src/App.tsx - Console routes
frontend/src/components/Main.tsx - Authentication flow
frontend/src/utils/auth.ts - Console API client
frontend/src/api/API.ts - App management
frontend/src/components/Applications - Group management
frontend/src/components/Groups - Instance monitoring
frontend/src/components/Instances - Activity timeline
frontend/src/components/Activity - Package management
frontend/src/components/Packages
Update delivery
- Omaha protocol
backend/pkg/omaha/omaha.go - Update syncer
backend/pkg/syncer/syncer.go - Update handlers
updater
Other components
- Operator
- Omaha instance
Connections 27
- Operator → Console bootstrap: manages rollouts
README.md - Omaha instance → HTTP handlers: requests updates
README.md - Application startup → HTTP server: starts
backend/cmd/nebraska/main.go - Application startup → Admin service: constructs
backend/cmd/nebraska/main.go - Application startup → Runtime service: constructs
backend/cmd/nebraska/main.go - Application startup → Update syncer: starts optionally
backend/cmd/nebraska/main.go - HTTP server → HTTP handlers: registers routes
backend/pkg/server/server.go - HTTP handlers → Admin service: invokes
backend/pkg/handler/handler.go - HTTP handlers → Runtime service: invokes
backend/pkg/handler/handler.go - HTTP handlers → Omaha protocol: constructs handler
backend/pkg/handler/handler.go - HTTP handlers → Application routes: implements routes
backend/pkg/handler/handler.go - Application routes → Admin service: writes app data
backend/pkg/handler/app.go - Application routes → Read queries: reads app data
backend/pkg/handler/app.go - Admin service → Application database: writes records
backend/pkg/api/admin/applications.go - Read queries → Application database: queries records
backend/pkg/api/internal/dbreads/applications.go - Runtime service → Read queries: uses queries
backend/pkg/api/runtime/service.go - Console bootstrap → Console API client: loads configuration
frontend/src/App.tsx - Console bootstrap → Console routes: renders routes
frontend/src/App.tsx - Console routes → Authentication flow: guards routes
frontend/src/components/Main.tsx - Console routes → App management: routes to
frontend/src/components/Main.tsx - Console routes → Group management: routes to
frontend/src/components/Main.tsx - Console routes → Instance monitoring: routes to
frontend/src/components/Main.tsx - Console bootstrap → Console API client: requests data
frontend/src/App.tsx - Console API client → Application routes: calls endpoints
- Update syncer → Admin service: uses admin service
- Omaha protocol → Runtime service: serves update flow
- Update handlers → Omaha instance: delivers update response