{"id":17356783,"url":"https://github.com/thujuli/ngivent","last_synced_at":"2026-04-11T01:47:51.176Z","repository":{"id":235754458,"uuid":"791172418","full_name":"thujuli/ngivent","owner":"thujuli","description":"Ngivent is an innovative web platform that connects ticket sellers with users who want to buy tickets for their favorite events. With a range of features supporting both sellers and users, Ngivent provides a complete solution for event ticket management and purchase.","archived":false,"fork":false,"pushed_at":"2024-05-21T09:25:27.000Z","size":20850,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-02-01T19:23:26.490Z","etag":null,"topics":["express","jest","multer","nextjs","prisma","react-hook-form","recharts","shadcn-ui","sonner","supertest","tailwindcss","tanstack-react-query","tanstack-table","zod"],"latest_commit_sha":null,"homepage":"","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/thujuli.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-04-24T08:18:22.000Z","updated_at":"2024-05-21T13:53:30.000Z","dependencies_parsed_at":"2024-05-15T19:27:48.494Z","dependency_job_id":"eb43560f-a2b4-4e48-89f9-d3e5a3361b16","html_url":"https://github.com/thujuli/ngivent","commit_stats":null,"previous_names":["thujuli/event-minpro"],"tags_count":0,"template":false,"template_full_name":"purwadhikafullstack/finpro-nextjs-express-prisma","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/thujuli%2Fngivent","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/thujuli%2Fngivent/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/thujuli%2Fngivent/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/thujuli%2Fngivent/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/thujuli","download_url":"https://codeload.github.com/thujuli/ngivent/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245872511,"owners_count":20686398,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["express","jest","multer","nextjs","prisma","react-hook-form","recharts","shadcn-ui","sonner","supertest","tailwindcss","tanstack-react-query","tanstack-table","zod"],"created_at":"2024-10-15T18:58:43.511Z","updated_at":"2026-04-11T01:47:46.123Z","avatar_url":"https://github.com/thujuli.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Purwadhika Final Project Repository\n\nThis project uses React.js with NextJS for the frontend, Express.js for the backend, and TurboRepo for monorepo management, facilitating rapid development of a scalable web application with streamlined collaboration and efficient server-client interactions.\n\n## Available Scripts\n\n### `npm run dev`\n\nRuns the app in the development mode.\n\nOpen [http://localhost:5173](http://localhost:5173) to view it in the browser. For API, you can access it in [http://localhost:8000/api](http://localhost:8000/api). The app will reload if you make edits.\n\n### `npm run build`\n\nBuilds the app for production to the `dist` folder for each project.\n\n### `npm run serve`\n\nRuns the app in the production mode.\n\n### `npm run \u003ctask\u003e --workspace=\u003capp-name\u003e`\n\nRun command on specific app (install package, run test, etc).\n\n### `npm run \u003ctask\u003e --workspace=\u003capp-name\u003e -- --\u003coption\u003e`\n\nRun command on specific app with options.\n\nExample : `npm run seqeulize --workspace=api -- --db:migrate`\n\n# Rules\n\n## Commit \u0026 Pull Request\n\n- Always use [conventional commit message](https://www.conventionalcommits.org/en/v1.0.0/) when committing changes or creating pull request\n- **\"Squash and Merge\"** your pull request to main branch\n\n## Naming Convention\n\n### REST API\n\n- Always use [REST API naming convention](https://restfulapi.net/resource-naming/)\n\n### File Naming Conventions:\n\n1. **Use CamelCase for filenames:**\n\n   - Begin filenames with a lowercase letter.\n   - For multiple words, capitalize the first letter of each subsequent word.\n   - Example: `index.js`, `userModel.js`, `dataAccess.js`\n\n2. **Use Descriptive Names:**\n\n   - Choose names that accurately describe the file's purpose or content.\n   - Avoid overly generic names like `utils.js` unless the file genuinely contains utility functions.\n\n3. **Follow Naming Conventions for Specific File Types:**\n\n   - For configuration files, use names like `.env`, `config.js`, or `settings.json`.\n   - Use consistent naming for test files, such as appending `.test.js` or `.spec.js` to the filename being tested.\n   - Use `package.json` for the project's metadata and dependencies.\n\n4. **Separate Concerns with File Naming:**\n   - Follow a modular structure for different concerns (e.g., `userController.js`, `userService.js`, `userModel.js` for a user-related module).\n\n### Folder Naming Conventions:\n\n1. **Use Singular or Plural Naming:**\n\n   - Choose a consistent convention for naming folders (e.g., `models` or `model`, `routes` or `route`).\n\n2. **Avoid Special Characters and Spaces:**\n\n   - Use hyphens (`-`) or underscores (`_`) for separating words in folder names, but avoid spaces or special characters.\n\n3. **Use Descriptive Names for Folders:**\n\n   - Name folders according to their content or purpose (e.g., `controllers`, `services`, `utils`, `tests`, `public`, `views`, etc.).\n\n4. **Nested Folder Structure:**\n   - Create a logical and organized folder structure based on the project's architecture.\n   - For larger projects, consider organizing files by features/modules (Feature-Based Structure) or layer-based (Layered Structure).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fthujuli%2Fngivent","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fthujuli%2Fngivent","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fthujuli%2Fngivent/lists"}