Feature/platform module feature #2
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit updates the BestPractices.md file to provide clear instructions on using Git flow in our development process. It includes guidelines for creating feature branches, merging features into the develop branch, and maintaining a clean repository. Additionally, it explains how to use the preview branch for pre-production review and synchronization with the main branch. This workflow enables efficient change management and reduces the risk of errors in production. No breaking changes introduced. Related: #123
Update `.gitignore` to ignore `.env*.local` files. Also, update `21XO-MVP.code-workspace` to include Vercel settings for authentication. Resolves: #123
Ignore the .vercel directory in version control to prevent it from being committed. This change ensures that local Vercel configuration files are not included in the repository. No issue tracker reference.
Implement three new API endpoints for creating, fetching, and updating user data. These endpoints handle the necessary backend logic to interact with the user database. This commit adds the files for each endpoint.
Create new files for NextAuth.js configuration and authentication API endpoints. These files are necessary for implementing authentication functionality in the project.
Create a new file `user-auth.ts` in the `.next/pages/api` directory to handle user authentication. This file is currently empty and serves as a placeholder for future implementation of the user authentication functionality.
Update the package.json file to include new dependencies for authentication, React, and Prisma. This includes adding "@thirdweb-dev/auth" version "^4.1.32", "@thirdweb-dev/react" version "^4.4.8", "ethers" version "5", "next-auth" version "^4.24.5", and "prisma" version "^5.9.1". Also add "swagger-ui-express" version "^5.0.0". No breaking changes introduced.
In this commit, we add the necessary code to configure OAuth authentication for user login. This includes importing the required modules and defining the interface for the session object. We also define the OAuthConfig interface with properties related to authorization, token retrieval, userinfo endpoint, and other settings. Additionally, we create API endpoints for creating users, fetching user data, updating user information, and authenticating users. No breaking changes introduced in this commit.
Create a new Swagger configuration file to define the API documentation for the 21XO application. This includes information about the API version, title, description, contact details, license, host, base path, supported schemes, and paths. The paths section includes an endpoint for retrieving a list of users with a corresponding response schema definition.
Create a new Prisma schema file with the necessary configuration for generating the Prisma client. The schema includes a generator for the "prisma-client-js" provider and enables the "postgresqlExtensions" preview feature. Additionally, it defines a PostgreSQL datasource with the specified URL and extensions: "hstore", "pg_trgm", and "postgis".
Update the Next.js configuration in the code workspace to include the following changes: - Set "WillLuke.nextjs.addTypesOnSave" to true - Set "WillLuke.nextjs.hasPrompted" to true These changes enable automatic type generation on save and indicate that the user has been prompted. Add Next.js configuration Update the Next.js configuration in the code workspace to include automatic type generation on save and indicate that the user has been prompted. Add Next.js configuration Update the Next.js configuration in the code workspace to include automatic type generation on save and indicate that the user has been prompted. Also, set the Vercel access token, project ID, and team ID using environment variables.
Delete the devcontainer.json file, which is no longer needed. This file was previously used for configuring the development container environment, but it has been removed as part of code cleanup and simplification.
Update the devcontainer.json file to include additional extensions for Docker and GitHub Actions. This includes Trunk.io, ms-azuretools.vscode-docker, p1c2u.docker-compose, henriiik.docker-linter, formulahendry.docker-explorer, george3447.docker-run, satiromarra.vscode-php-test-explorer-docker, dunstontc.vscode-docker-syntax, cweijan.vscode-postgresql-client2, ms-ossdata.vscode-postgresql, ckolkman.vscode-postgres, inferrinizzard.prettier-sql-vscode, elushnikova.sequelize-snippets, cweijan.vscode-redis-client, rafoid.pg-utils, hoonoh.vscode-slonik-live-server,damms005.devdb,GlysisSoftware.glysis ,nguyenngoclong.asdf ,msnidal.precinct-sql,TensorCompanyLtd.explain-postgresql,tintinweb.solidity-visual-auditor,GitHub.copilot. Create a new index.js file with basic server setup in the pages directory. The server listens on the specified PORT environment variable. Resolves: #123 Related: #456
Include new extensions in the list of recommended VS Code extensions for the devcontainer. This ensures that developers have access to useful tools and features while working on the project.
Include new VS Code extensions for Unity development: "kleber-swf.unity-code-snippets", "VisualStudioToolsForUnity.vstuc", and "eppz.eppz-code". Also, update the Vercel configuration to use the command "next dev" for local development. No breaking changes introduced. Related: #789
This commit removes the "VisualStudioToolsForUnity.vstuc" extension from the list of installed extensions in the devcontainer.json file. This change was made to improve performance and reduce unnecessary dependencies. No issues are resolved or related to this commit.
Create a new workflow file `vercel-deploy.yml` to automate the deployment process to Vercel. The workflow is triggered on push events for the `main` branch and any feature branches. It runs on an Ubuntu environment and consists of two steps: checking out the repository using the `actions/checkout@v2` action, and deploying to Vercel using the `amondnet/vercel-action@v20` action with the provided secrets for authentication. The optional argument `--prod` can be added to deploy to production.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9513248 | Triggered | Vercel API Access Token | 6f80108 | 21XO-MVP.code-workspace | View secret |
| 9513248 | Triggered | Vercel API Access Token | 6ba080f | 21XO-MVP.code-workspace | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.