CloudAEye for 
OneDrive
Your team already documented it. Now new developers can find it.
Your setup guides, decision records, and runbooks already explain how things work. CodeCortex reads them alongside your code, so new developers get answers instead of a reading list.
Sign in with Microsoft You choose the folders
OneDrive · example onboarding question
Local development
Use the dev container. It includes Postgres and a stub of the payment provider.
Copy .env.example to .env and run make dev, then load test accounts with make seed.
Request staging credentials in #platform-access.
Indexed from a folder you selected.
New
developerHow do I run the service locally?
Copy .env.example to .env and run
make dev. It starts Postgres and the provider stub
from docker-compose.dev.yml.
make seed loads test accounts from
scripts/seed.py.
ADR-007: Primary datastore
Status: accepted.
Ledger writes need transactions across rows. We chose Postgres for transactional integrity over DynamoDB's simpler scaling.
Revisit if write volume outgrows a single primary.
Indexed from a folder you selected.
New
developerWhy do we use Postgres instead of DynamoDB?
ADR-007 chose Postgres because each refund updates the payment
and ledger rows together. You'll see it in the
db.transaction() blocks across
services/ledger/.
Refund queue backlog
Alert: queue depth above 500 for 10 minutes.
Check the provider's status first. If it's healthy, scale refunds-worker up. Never purge the queue.
Escalate to #payments-oncall after 30 minutes.
Indexed from a folder you selected.
New
developerWhat do I do if the refund queue backs up?
The runbook starts with the provider's status page. If it's
healthy, scale refunds-worker; its replica count is
set in deploy/refunds-worker.yaml. Purging the
queue drops customer refunds.
Accurate answer from the team's knowledge.
Google Drive
YouTubeConnect once.
Every new hire benefits.
Set it up once in the CloudAEye console. After that, new developers just ask.
-
Week one:
get oriented.Learn the services, the setup, and the architecture from the documents your team already keeps, without waiting for someone to walk you through it.
First-week questions -
First change:
know the why.Before touching unfamiliar code, find the decision record, runbook, or convention that shaped it.
First-change questions -
Every hire after:
answer once.Point new teammates to CodeCortex. The explanation you wrote once keeps answering.
Ongoing questions
You choose
what gets indexed.
Select folders and files. Everything else in your OneDrive stays out of CodeCortex.
26 files in 3 folders will be indexed.
CodeCortex indexes
- Word (.docx) and PDF
- Markdown, reStructuredText, plain text, and logs
- CSV, JSON, YAML, and XML
Questions new developers
would otherwise ask you.
The questions that usually go to whoever has been here longest, answered from the documents your team already keeps.
Get a working local environmentFirst week
Follow the setup guide with the commands, config files, and access requests it mentions, mapped to the repository.
How do I run the service locally?
Where do I get staging credentials?
Learn the architecture from the overviewFirst week
Read the system overview your team keeps in OneDrive alongside the services and directories it describes.
What are the main services and how do they talk?
Understand a past decisionFirst change
Find the decision record behind a technology choice before you work against it.
Why do we use Postgres instead of DynamoDB?
Follow the runbookFirst change
See the steps, thresholds, and escalation path for an alert in the service you're changing.
What do I do if the refund queue backs up?
Check conventions before your first PRFirst change
Find the team's coding and review conventions and how they apply to the files you're about to change.
What are our API naming conventions?
Stop answering the same question twiceOngoing
Link the question to the document instead of retyping the answer. Every later hire gets the same explanation.
Where's the architecture overview?
Which document covers our release process?
Your next new hire.
A faster first week.
Onboard developers in days, not months. Create a CloudAEye account, connect OneDrive, and choose the folders a new developer should learn from.
Connect OneDrive Talk to our team-
1
Sign in to CloudAEye
Create an account or sign in to the CloudAEye console.
-
2
Connect OneDrive
Sign in with Microsoft and approve the consent screen.
-
3
Choose folders, then ask
Select the folders and files to index. When indexing finishes, ask it the questions a new developer would.
A few things worth knowing.
What access does CloudAEye request?
Microsoft's consent screen asks for read and write access to your
files (Files.ReadWrite.All) and your basic profile
(User.Read). CloudAEye uses it only to list folders
and download the files you select. It never creates, changes, or
deletes anything in your OneDrive.
Is my whole OneDrive indexed?
No. Only the folders and files you select are indexed. Choose your engineering documents and leave everything else out.
Which files get indexed?
Word (.docx) and PDF; Markdown, reStructuredText, plain text, and logs; CSV, JSON, YAML, and XML.
Can I remove a file after it's indexed?
Yes. Remove an indexed file and CloudAEye deletes its indexed copy. Files are removed one at a time, not by folder.
What happens if I disconnect OneDrive?
CloudAEye deletes the stored connection and everything it indexed from your OneDrive.