docs: add environment setup note for Docker installation - #366
docs: add environment setup note for Docker installation#366Mohit-001-hash wants to merge 1 commit into
Conversation
PR Context Summary
Suggested issue links
Use |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe README’s environment setup section now instructs contributors to copy ChangesEnvironment setup documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| ``` | ||
|
|
||
| From repository root: | ||
| ``` |
There was a problem hiding this comment.
🟢 Low README.md:114
The extra ``` line at line 114 opens a Markdown code fence before the existing ```bash block. As a result, the inner ```bash fence and its language marker render as literal text instead of a syntax-highlighted Docker command block, degrading the installation instructions. Remove the standalone ``` line so the ```bash block renders normally.
| ``` |
🤖 Copy this AI Prompt to have your agent fix this:
In file @README.md around line 114:
The extra ` [code fence] ` line at line 114 opens a Markdown code fence before the existing ` [code fence]bash ` block. As a result, the inner ` [code fence]bash ` fence and its language marker render as literal text instead of a syntax-highlighted Docker command block, degrading the installation instructions. Remove the standalone ` [code fence] ` line so the ` [code fence]bash ` block renders normally.
ApprovabilityVerdict: Needs human review Documentation-only change to README.md, but the author is not the designated code owner (owned by Abhash-Chakraborty). Additionally, there's an unresolved review comment about a markdown formatting issue (extra code fence at line 114) that would break rendering of installation instructions. You can customize Macroscope's approvability policy. Learn more. |
|
Thanks — the
Something like this is all it needs: ### Option A: full real-ML stack
From repository root, copy the example environment file and adjust it before starting the stack:
```bash
cp .env.example .env
```
Then:
```bash
docker compose up --build
```
Fix the fence and I'll merge it. |
|
@macroscope-app review Please review this PR against its linked issue, local-first privacy rules, and the current Find repo instructions. |
|
This PR is marked as stale. It will close automatically after 7 days without renewed activity; remove the stale label when work resumes. |
Summary
Added a missing environment setup note to the Docker installation section, reminding contributors to configure the
.envfile before running Docker commands. This improves the setup instructions and helps prevent configuration-related issues.Contributor PRs must target
canary. Only the maintainer promotion PR fromcanarymay targetmain.Fixes #None (just a documentation quick fix)
Type of change
Release impact
What changed
.envfile before executing Docker commands.Screenshots / recordings (for UI changes)
N/A
How to test
Checklist
canaryunless it is the maintainer promotion PRGSSoC'26 checklist
Summary by CodeRabbit