### TL;DR
Added new keys for Google and Turnkey integration in `local.toml.example`
### What changed?
- Updated server session secret to empty string
- Added placeholders for google clientId and clientSecret
- Added placeholders for Turnkey API integration (apiBaseUrl, apiPrivateKey, apiPublicKey, defaultOrganizationId)
### How to test?
1. Pull the latest changes
2. Update `local.toml.example` file with actual values.
3. Run the application locally and ensure all services are working correctly.
### Why make this change?
To integrate new services (Google and Turnkey) into the project setup.
---
### TL;DR
- Still cretaes app if user migrates from page
The PR introduces a new `AddProjectFromTemplate` mutation to facilitate project creation using a repository template. This change centralizes the template project creation logic within the backend, improving code maintainability by removing redundant client-side code.
### What changed?
- Added `AddProjectFromTemplate` input type in `schema.gql` and corresponding TypeScript interfaces.
- Implemented `addProjectFromTemplate` resolver with error handling and Octokit integration for repository creation.
- Updated `service.ts` to include the new `addProjectFromTemplate` method.
- Created new GraphQL `Mutation` for `addProjectFromTemplate` in the GraphQL schema.
- Adjusted the client-side GQLClient to support the new mutation.
- Modified frontend to utilize the new backend mutation for project creation from a template.
### How to test?
1. Ensure your backend server is running.
2. Use a GraphQL client like Postman to call the `addProjectFromTemplate` mutation with appropriate input.
3. Verify that the new project is created using the specified template, and appropriate error messages are returned for failures.
4. Check the frontend flow for creating a project from a template to ensure it is working correctly.
### Why make this change?
This change enhances code maintainability by centralizing template project creation logic within the backend, thereby reducing redundancy and potential inconsistencies in client-side implementations.
---
This pull request refactors the main `README.md` by removing detailed backend and frontend setup instructions and adding separate `README.md` files for the backend and frontend with their specific setup and deployment instructions. This makes the main `README.md` cleaner and directs users to specific READMEs for backend and frontend setups.
---
### TL;DR
Implemented the new `VerifyCodeInput` component and updated the access code validation logic.
### What changed?
1. Added a new reusable `VerifyCodeInput` component for verifying codes in a user-friendly way. This component handles paste events, input changes, and keyboard navigation.
2. Updated the backend route `/accesscode` to accept an arbitrary code for now.
3. Incorporated the `VerifyCodeInput` component into the `AccessCode` page, replacing the generic `Input` component.
4. Updated the access code validation logic to check for a trimmed length of 5 characters instead of 6.
5. Added a slight pause for UX purposes when validating the access code on the frontend.
### How to test?
1. Go to the Access Code page.
2. Try entering an access code with various inputs (keyboard, paste, etc.) to see if it works seamlessly.
3. Verify that only a 5-digit code is considered valid.
4. Check the backend logs to ensure the validation endpoint is working as expected.
### Why make this change?
This change improves the user experience by providing a custom input component for access code verification and ensures that the access code validation meets the new requirements.
---
## What changed?
This Pull Request introduces an access code validation feature to the authentication process. Changes encompass backend route for access code validation, new frontend components for handling access code input, and integration of the access code verification in the signup flow.
### Backend:
- Added POST `/accesscode` route in `auth.ts` for validating access codes.
### Frontend:
- Created `AccessCode` component for access code input and validation.
- Added `AccessSignUp` component that integrates access code verification before signup.
- Updated `SignUp` component to check for valid access code on mount.
- Modified `SnowballAuth` to use new `AccessSignUp` instead of `SignUp`.
- Added `verifyAccessCode` utility function for code verification API call.
## How to test?
1. Run the backend and frontend projects.
2. Navigate to the signup page. You should be prompted to enter an access code.
3. Enter the code `444444` and proceed. Any other code should display an error message.
4. Verify that valid access code routes to the signup component.
## Why make this change?
This change improves authentication by adding an extra layer of security through access code verification.
* Fix format of eth address to display
* Set authority for record name from backend config
* Add functionality to open repo button
* Use commit author image and commit url in activity card
* Handle review changes
* Fix commit author as null
* Add timeout to move to next page on project creation
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Create web3 modal provider with SIWE
* Add auth router to handle SIWE authentication
* Use axios instance to make request
* Add button for SIWE authentication
* Add changes to access session in web-app GQL requests
* Add auth check in GQL context and load/create user
* Use authenticated user from context
* Redirect to sign in page if unauthenticated and logout button
* Change sign-in route to login
* Get project domain from config file
* Set user ethAddress column as unique
* Use formatted user name
* Get session secret and origin url from config file
* Add unique constraint for eth address
* Get secure and samesite from origin url
* Get wallet connect id and backend url from env file
* Format user email in member tab panel
* Add backend config isProduction to set trust proxy
* Use only one server url config
* Add tool tip for displaying email
* Add trustProxy and domain in server.session config
* Add SERVER_GQL_PATH constant in frontend
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Fix alignment of deployment status chip
* Use template name from env
* Use env for git template link
* Add loading spinner for create project
* Display user name
* Format the displayed user name
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Create application deployment request on new deployment
* Save application deployment request datas in deployment entity
* Add project as dependency
* Use project repo name as record app name
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Populate organization and user if db is empty
* Use hardcoded user id from fixtures
* Implement polling for get deployments query
* Handle review changes
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add method to update multiple deployments in single query
* Fix deployments URL visit and date filter
* Clean fixtures data
* Update fixtures data
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add skeleton and TODOs for polling deployment records
* Add method implementations for fetching deployment records
* Handle if deployment url is not set
* Add logs after getting ApplicationDeploymentRecord
* Add application deployment record to deployment entity
* Change type of application deployment record data
* Fetch delay to check deployment records from config
* Update isCurrent after deployment record received
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Create repo webhook and express handler for webhook
* Create deployments from commits in GitHub
* Update isCurrent in previous production deployment
* Create script for setting authority
* Update README for initialize registry script
* Handle review changes
* Use correct repo URL in record data
* Handle github unique webhook error
* Handle async execution of publishing records
* Update readme with ngrok setup
* Review changes
* Add logs for GitHub webhooks
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Handle request error while fetching Git activity
* Use default Octokit instance if auth token is not available
* Rename input arguments of mutation methods to data
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Display commit message in projects and deployments
* Handle if current deployment not present
* Rename types file
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Get latest commit hash from repo when adding project
* Update UI/UX
* Fill registry record with data from package.json
* Add package json type
* Correct record data based on laconic console
* Update README
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add routes to settings tab panel
* Refactor code to move settings tab components to pages
* Rename registry fields in project and deployment entity
* Use kebab case for routes
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add routes to project tabs
* remove react tabs and use material tailwind component instead
* Refactor code to move project tab panels in pages directory
* Remove unused function from database class
* Refactor routes for project tabs
* Publish record in laconic registry on creating project and deployment
* Refactor publish record method
* Set name for the published record
* Publish application deployment request
* Add README for publishing record
* Add await in add project resolver method
* Update meta data for deployment request record
* Remove title field from deployment entity
* Refactor service and registry class for publishing record
* Add record data to project and deployment entity
* Set record id and data as nullable in project entity
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Create new deployment when changing to production
* Remove unnecessary todos
* Move deployment id and url creation in database method
* Display correct details in deployment dialog box
* Rename relativeTime function to relativeTimeISO
* Refactor resolver methods to service class
* Refactor to move github app to service class
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Create repository from selected template
* Create project based on created repository
* Replace dropdown component with component from material tailwind
* Remove repository name from query parameters
* Implement dropdown for organizations switcher
* Add dynamic route for organization id
* Update routes for organization slug
* Use organization slug for adding project
* Refactor to fetch organizations at sidebar component
* Update organization switcher based on searched project
* Refactor types in frontend
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Implement functionality to visit deployment
* Check and display domain details in overview tab for production branch
* Update fixtures to remove project name from deployment url
* Refactor and add uuid to typeorm entities
* Fix deployment url
* Display live domain details in project overview
* Use database query to fetch live production domain
* Remove unused methods from backend utils
* Set project name from repo organization and name when creating project
* Rename success and project components according to routes
* Display URL for change to production dialog box
* Refactor database method for domains to service class
* Handle error in resolver instead of service class
* Return entity from service class for add operation
* Do not fetch branches if repo not available
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Refactor mutation methods to service class
* Refactor database methods to service class
* Display organization name in sidebar
* Handle review comments
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Display current deployment info in overview tab
* Add assign domain dialog box in deployments
* Add empty link for project settings in assign domain dialog box
* Use react router dom link
* Add sub domain to project entity
* Add deployment url with custom generated string
* Set nano id to deployment id
* Add sub domain while creating new project
* Use same id as in url
* Update readme steps for production build
* Update README
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add Service class and use in GQL resolver
* Refactor resolver query methods to service class
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add GQL mutation for transfer project
* Integrate transfer project GQL client method
* Use update project GQL method for transfer project
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add mutation for adding project member
* Add GQL client method for add project member
* Handle review comments
* Integrate add project member GQL client method
* Handle cascades for project members and user organizations
* Add null type to user.name and domain.redirectTo
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Make use of domain id for redirecting domains
* Add checks in backend to prevent chain redirecting and editing redirected domain
* Add self relation to domain entity and use it to create and edit domains
* Add self referencing relation to initialize db script
* Add redirectToId column in domain entity
* Remove isRedirected flag from domain entity
* Refactor edit domain dialog box
* Use dummy data for repository
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add mutation to update permissions of project member
* Use update project member permission client method in UI
* Handle review changes
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Use react-oauth-popup for github authentication popup
* Fetch auth token and use in app to fetch list of repositories
* Get client id and secret from config
* Use GitHub search API for fetching repos
* Use debounce for searching repos and projects
* Change environment field to enum instead of array
* Update gql client for get environment variables query
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add and use createdBy field in deployment entity
* Use updated get deployments client method in UI
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Use rollback deployment client in UI
* Check if deployements domain is undefined
* Fix typo
* Rename variable to current deployment
* Handle deployment domain relation on rollback
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Pass data for all domains in edit domain dialog box
* Add mutation to update domain by id
* implement front end and gql client method to edit domain
* Rename arguments of resolver function to update domain and project
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add mutation to create new domain
* Update mutation to create two domains for www and non-www variant
* Add gql-client method and frontend to create domain
* Display fetched domains in domains tab panel using project id
* Fix graphql type for fetching domains
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Show project owner in member tab panel
* Implement mutation for rollback deployment
* Fix project members count
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Implement delete project functionality
* Use delete project client method in UI
* Refetch projects information on deleting project
* Use project's current deployment domain name for url
* Handle review changes
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Fix deployment creation time and hard coded title
* Add delete database script
* Use database file path from config file
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add graphql mutation to redeploy deployment to production
* Implement frontend to redeploy deployment to production
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Add mutation to update deployment to production
* Implement gql client mutation and frontend to update deployment to production
* Add toast message when deployment is changed to production
* Throw error from init db script if db aleardy exists
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Find projects based on search text
* Use get search projects client method in UI
* Fetch searched projects inside useCombobox hook
* Get searched project from project entity
* Remove non required search projects filtering
* Fetch projects if user is owner or project member
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
