[DEVOPS] Audit .gitignore for missing entries

[dev-fatima-24]

Priority: medium

Description

The .gitignore is missing entries for several generated files and directories: Rust build artifacts (target/), Python virtual environments (.venv/), Next.js build output (.next/), and Prisma generated client. Without these, contributors may accidentally commit large generated files or secrets.

Acceptance Criteria

• target/ directory excluded for Rust contracts
• .next/ and out/ excluded for Next.js
• node_modules/ excluded at root and in all subdirectories
• .venv/ and pycache/ excluded for Python oracle
• .env files excluded (only .env.example is committed)

[obswrld]

@obswrld has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Here's your application:

Why I'd like to work on this issue:
Missing .gitignore entries are a silent risk — one accidental commit of target/ or a .env file can expose secrets or bloat the repo permanently. This is a small but high-impact fix that protects every future contributor.
Relevant experience:

Stellar Wave Program contributor across multiple repos spanning Rust/Soroban, Next.js, and Python codebases — giving me direct familiarity with all four artifact types this issue covers
agri-fi #156 and teachLink_backend #641 — worked inside NestJS/Node backends, familiar with node_modules/ and .env exclusion patterns
akkuea #847 application — Soroban/Rust contract deployment work, familiar with target/ build artifacts
SYNCRO #482 — Next.js frontend work, familiar with .next/ and out/ build output
TrustLink #540 application — Python async client work, familiar with .venv/ and pycache/ exclusions

My approach:

Read the existing .gitignore fully before making any changes
Add target/ for Rust contracts
Add .next/ and out/ for Next.js
Add node_modules/ at root and subdirectory level
Add .venv/ and pycache/ for Python
Add .env* with exception for .env.example
Verify no currently tracked files are affected

Ready to start immediately upon assignment.
@dev-fatima-24/carbonledger

ℹ️ Repo Maintainers: To accept this application, review their application or assign @obswrld to this issue.

[ekelemepraise-code]

@ekelemepraise-code has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Can I work on this issue ? ETA - 6hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ekelemepraise-code to this issue.

[drips-wave]

Congratulations, @ekelemepraise-code! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @ekelemepraise-code: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊