How bytegeniusitu/back-end-hosting works
Project type and purpose
• Its primary responsibilities are to expose dashboard and deployment HTTP endpoints, respond to health checks, and record telemetry.
File structure
• Top-level artifacts:
• Dockerfile, .dockerignore – service is containerized.
• GitHub workflows – CI/CD is set up to build, test, and push images.
• Cargo.toml/Cargo.lock – Rust crate manifest.
• src/ – application code:
– configuration.rs – loads runtime config (env vars, files).
– telemetry.rs – sets up logging/tracing.
– startup.rs – composes server, middleware, telemetry, config.
– routes/mod.rs + dashboard.rs, deploy.rs, health_check.rs – HTTP handlers.
– lib.rs – reusable library entrypoints.
– main.rs – binary entrypoint.
• tests/ – integration test for health_check.
(empty) README for additional insights
• README is empty, so infer architecture solely from code organization and CI files.
Detail and coverage
• Every top-level element (CI/CD, container registry, orchestrator).
• Zoom into the container: show how configuration.rs is wired into startup.rs, how telemetry.rs is initialized before the HTTP server, and how each route module plugs into the router.
• Notes on port numbers or environment variables if relevant (e.g., SERVER_PORT).
• Do not omit the tests folder—in a separate callout, indicate the existence of integration tests against health_check.