fix: Enable Link-Time Optimization (LTO) and codegen-units = 1 for Release builds

[RambokDev]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated build optimization settings for release builds to improve performance and reduce binary size.
  • Updated production deployment configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates build and deployment configurations. The Cargo.toml receives a new release profile section with optimization flags (link-time optimization, reduced codegen units, and stripped debug information). The docker-compose.prod.yml file updates the EDGE_KEY value and corrects YAML formatting.

Changes

Cohort / File(s)	Summary
Build Release Profile Cargo.toml	Added [profile.release] section with optimizations: lto = true, codegen-units = 1, and strip = "debuginfo" for production builds.
Docker Compose Configuration docker-compose.prod.yml	Updated EDGE_KEY value from long token to shorter base64-encoded string; fixed YAML indentation and removed extraneous whitespace.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related issues

• Main issue adds the same Cargo.toml release profile settings (lto and codegen-units) proposed in this PR, indicating these changes address the same optimization objectives.

Poem

🐰 Hops through configs with glee,
LTO and strips set the binary free,
EDGE_KEY reborn, so compact and bright,
Production grows lean, burning light! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: enabling LTO and codegen-units optimization in Cargo.toml for release builds, which is the primary modification shown in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/cargo-build-release-optimization

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can customize the tone of the review comments and chat replies.

Configure the tone_instructions setting to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docker-compose.prod.yml`:
- Line 17: The docker-compose entry exposes a hardcoded secret via the EDGE_KEY
environment variable; remove the literal value and instead reference an injected
secret/env var (e.g., EDGE_KEY) so the compose file reads from the runtime
environment or Docker secrets rather than embedding credentials; update the
compose service's environment block to use an environment variable substitution
or a secrets: reference and ensure any deployment manifests or CI/CD secrets
store provides the actual EDGE_KEY at deploy time; search for EDGE_KEY to find
and replace the hardcoded line and validate local development with a .env or
secret stub that is not committed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a72e640d-e97c-4773-9353-5adbcca2f866

📥 Commits

Reviewing files that changed from the base of the PR and between e602c35 and 2213558.

📒 Files selected for processing (2)

• Cargo.toml
• docker-compose.prod.yml

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!