Part of [Service provider auctions for web deployments](https://www.notion.so/Service-provider-auctions-for-web-deployments-104a6b22d47280dbad51d28aa3a91d75)
- Implement funtionality to pay for deployments by connecting wallet using `WalletConnect`
Co-authored-by: IshaVenikar <ishavenikar7@gmail.com>
Co-authored-by: Shreerang Kale <shreerangkale@gmail.com>
Reviewed-on: cerc-io/snowballtools-base#17
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: cerc-io/snowballtools-base#11
* 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>
* 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>
* 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>
* Add Service class and use in GQL resolver
* Refactor resolver query methods to service class
---------
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
* 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>
