### TL;DR Integrates project data fetching for dynamic subdomain display on the Project Deployment Success page and the OverviewTabPanel. ### What changed? - Updated `Id.tsx` to fetch project data and dynamically display project's subdomain after deployment. - Modified `Overview.tsx` to make project's subdomain a clickable link. ### How to test? 1. Deploy a new project and check the deployment success page for correct subdomain display. 2. Open a project's overview tab and click the subdomain link to ensure it navigates correctly. ### Why make this change? Improves user experience by displaying the actual subdomain and making it clickable, ensuring users can conveniently verify their deployment and access project domain. --- |
||
|---|---|---|
| .. | ||
| .storybook | ||
| public | ||
| src | ||
| .env.example | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .node-version | ||
| .prettierignore | ||
| .prettierrc.json | ||
| chromatic.config.json | ||
| index.html | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| reload-dev.sh | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
frontend
This is a vite react nextjs project in a yarn workspace.
Getting Started
Install dependencies
In the root of the project, run:
yarn
Build backend
yarn build --ignore frontend
Environment variables
Local
Copy the .env.example file to .env:
cp .env.example .env
Staging environment variables
Change in deployer/deploy-frontend.staging.sh
Production environment variables
Change in deployer/deploy-frontend.sh
Run development server
yarn dev
Deployment
From the root of the project, run:
Staging
cd packages/deployer && ./deploy-frontend.staging.sh
Production
cd packages/deployer && ./deploy-frontend.sh
Deployment status
Check the status of the deployment here