Who it is forA contributor about to change the API, indexer, or price adapters who wants a clean baseline first.
The problemChanges to the indexer or API can break formatting, linting, tests, or the Prisma schema, and it is faster to find out before editing.
The outcomeA green make check run and a local .env.local file ready for development.
What you need first
- Git and a clone of NuvexNetwork/nuvex-services
- pnpm and make, for `pnpm install` and `make check`
- A Solana-compatible RPC URL (NUVEX_RPC_URL or NUVEX_SOLANA_RPC_URL)
- At least one Nuvex program id (NUVEX_ORACLE_CORE_PROGRAM_ID, NUVEX_ORACLE_REGISTRY_PROGRAM_ID, or NUVEX_VERIFICATION_PROGRAM_ID)
- A PostgreSQL DATABASE_URL, or a NUVEX_READ_MODEL_PATH for a JSON snapshot
Steps
- Clone the repository and change into its root folder.
- Run
pnpm install. - Run
make check. - Run
cp env/.env.local.example .env.localto create the local environment file.
Prompt for your agent
In the NuvexNetwork/nuvex-services repo, run `pnpm install` and then `make check`. Report which of the steps (format, lint, tests, Prisma schema validation) passed or failed, and quote the first error line if any. Do not start a database, since make check does not need one.
Caveat. make check does not start a database, so it cannot confirm that the indexer connects to Postgres.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page