|
| 1 | +# Contributing to Access Layer Server |
| 2 | + |
| 3 | +Thanks for contributing to the backend for Access Layer, a Stellar-native creator keys marketplace. |
| 4 | + |
| 5 | +## Before you start |
| 6 | + |
| 7 | +- Read the [README](./README.md) for context. |
| 8 | +- Review the scoped backlog in [docs/open-source/issue-backlog.md](./docs/open-source/issue-backlog.md). |
| 9 | +- Keep pull requests limited to one backend issue or one documentation improvement. |
| 10 | +- Open a discussion before changing core API shape or background processing architecture. |
| 11 | + |
| 12 | +## Local setup |
| 13 | + |
| 14 | +1. Install Node.js 20+ and `pnpm`. |
| 15 | +2. Copy `.env.example` to `.env`. |
| 16 | +3. Install dependencies: |
| 17 | + |
| 18 | +```bash |
| 19 | +pnpm install |
| 20 | +``` |
| 21 | + |
| 22 | +4. Generate Prisma client: |
| 23 | + |
| 24 | +```bash |
| 25 | +pnpm exec prisma generate |
| 26 | +``` |
| 27 | + |
| 28 | +5. Start the dev server: |
| 29 | + |
| 30 | +```bash |
| 31 | +pnpm dev |
| 32 | +``` |
| 33 | + |
| 34 | +## Verification commands |
| 35 | + |
| 36 | +```bash |
| 37 | +pnpm lint |
| 38 | +pnpm build |
| 39 | +``` |
| 40 | + |
| 41 | +Run `pnpm exec prisma generate` again whenever Prisma schema changes. |
| 42 | + |
| 43 | +## Backend contribution rules |
| 44 | + |
| 45 | +- Do not commit secrets, service accounts, or live credentials. |
| 46 | +- Use `.env.example` for safe placeholders only. |
| 47 | +- Keep API contracts explicit and documented. |
| 48 | +- Prefer clear domain names tied to Access Layer, not legacy template modules. |
| 49 | +- Add validation and error-handling behavior when introducing new endpoints. |
| 50 | + |
| 51 | +## Good first issue guidance |
| 52 | + |
| 53 | +Good first issues in this repo should: |
| 54 | + |
| 55 | +- avoid production credentials or third-party account dependencies |
| 56 | +- have a narrow API or documentation scope |
| 57 | +- include acceptance criteria and test instructions |
| 58 | +- avoid broad data model refactors |
| 59 | + |
| 60 | +## Questions |
| 61 | + |
| 62 | +If repo boundaries are unclear, confirm whether the work belongs in the client, server, or contracts repository before starting implementation. |
0 commit comments