GrantFox

Grants Open Source Platform.

---

Maintainers | Telegram

Joel Vargas | Frontend Developer JoelVR17 Telegram

Tech Rebel | Product Manager techrebelgit Telegram

Pablo Mora | Product Owner pmora3003 Telegram

Marco Araya | Backend Developer coxmars Telegram

---

Getting Started

Follow the steps below to get started with this project:

Summary

1. Install npm dependencies.
2. Create a Supabase Database. Tutorial
3. Prisma Migration. This video works too👆🏼
4. Run the Project.

Installation

1. Install dependencies:

   npm i

2. Lint and Format with Biome: (This is to ensure code quality and consistency)

   While Biome automatically lints and formats your staged files before each commit, you can also run these checks manually across the entire project using the following scripts:

   • To check for linting and formatting issues and apply automatic fixes:

     pnpm biome:fix
     # or
     pnpm biome

   • To only check for linting and formatting issues without applying fixes:

     pnpm biome:check

   • To only format the code without linting:

     pnpm biome:format

3. Generate the Prisma Model into Supabase

   npx prisma db push

4. Start the development server:

   npm run dev

Environment Variables

Make sure to set up the following environment variable in your .env file:

# SUPABASE -> Create a Supabase Database and copy the KEYS <-- See the Tutorial Video in Summary Section
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY=

# PRISMA <-- See the Tutorial Video in Summary Section
DATABASE_URL=
DIRECT_URL=

# TRUSTLESS WORK  <-- See the Video Below <-- Not necessary yet
NEXT_PUBLIC_API_URL=https://dev.api.trustlesswork.com
NEXT_PUBLIC_API_KEY=

API Key Video

dApp Trustless Work

408771125-33ea60b7-69b3-456a-afa6-56a7e70eb984.1.mp4

Wallet Requirements

To use this project, you must have one of the following wallets installed:

• Freighter
• Albedo
• xBull
• LOBSTR

These wallets are required to interact with the platform.

How to use a Wallet

You should use Chrome, Brave or Firefox browser, please install any of the wallets that were listen before. Important Note: If you're having problems to use Freighter, make sure that you have the wallet in "test net", and also if even you couldn't be able to use because it shows you "Not Available". Try going to: Security > Manage Connected Wallet > Remove the "localhost". If the problem persist, please contact us. This mistake happens for the wallet, not our product.

IMPORTANT NOTE: Code Quality and Commit Standards

This project uses Biome.js for code linting and formatting, and Husky to enforce code quality and commit message standards.

Here's how it works:

• Pre-commit Hook: Before any commit is finalized, Husky triggers Biome.js to automatically lint and format your staged files. If Biome finds issues that it cannot fix automatically, or if there are linting errors, the commit will be prevented. You'll need to resolve these issues before you can commit.
• Commit Message Validation: After you write your commit message and try to finalize the commit, Husky uses commitlint to ensure your message adheres to the Conventional Commits standard (e.g., feat: add new feature, fix: resolve bug). If your commit message is not correctly formatted, the commit will be rejected. You'll need to amend your commit message to meet the standard.

These integrations help maintain a clean, consistent codebase and a well-structured commit history. If a commit fails due to either of these checks, please review the error messages provided by Biome or commitlint and make the necessary corrections.