Part of [Service provider auctions for web deployments](https://www.notion.so/Service-provider-auctions-for-web-deployments-104a6b22d47280dbad51d28aa3a91d75)
- Fix request Id being set to `null` while fetching build logs
- Populate deployer LRNs dropdown with LRNs fetched from registry in configure delpoyment step
Co-authored-by: IshaVenikar <ishavenikar7@gmail.com>
Co-authored-by: Neeraj <neeraj.rtly@gmail.com>
Reviewed-on: #11
Part of [Service provider auctions for web deployments](https://www.notion.so/Service-provider-auctions-for-web-deployments-104a6b22d47280dbad51d28aa3a91d75)
- Add support for configuring web-app deployers by -
- Configuring deployer LRN (for targeted deployments)
- Configuring SP auction params for deployment auction (max price and number of providers)
Co-authored-by: IshaVenikar <ishavenikar7@gmail.com>
Reviewed-on: #2
### 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.
---
* 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>
* 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>
* Use Namespace import instead of named import
* Fix route for add domain
* Fix settings tab routes on changing sub path
* Fix stepper for add domain and project
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* 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>
* 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>
* 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>
* 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
* 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>
* Add graphql mutation to redeploy deployment to production
* Implement frontend to redeploy deployment to production
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
* Use update project gql client method in UI
* Handle save project button based on form change
* Fix import order
---------
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>
* Update root readme and setup depcheck
* Use fetched domain data in edit domain dialog box
* Use fetched project data in general tab
* Rename files in gql-client package
---------
Co-authored-by: neeraj <neeraj.rtly@gmail.com>
