bun run verify
bun run devURL: https://lovable.dev/projects/d92f5bad-8918-4827-a7b9-d4b9e8b466e9
There are several ways of editing your application.
Use Lovable
Simply visit the Lovable Project and start prompting.
Changes made via Lovable will be committed automatically to this repo.
Use your preferred IDE
If you want to work locally using your own IDE, you can clone this repo and push changes. Pushed changes will also be reflected in Lovable.
Install Bun 1.3.x before working locally. The repo pins bun@1.3.9, and the root install also covers the nested external/ workspace package.
Follow these steps:
# Step 1: Clone the repository using the project's Git URL.
git clone <YOUR_GIT_URL>
# Step 2: Navigate to the project directory.
cd <YOUR_PROJECT_NAME>
# Step 3: Install the necessary dependencies.
bun install
# Step 3a: Husky installs the pre-commit hook automatically during bun install.
# Step 4: Start the development server with auto-reloading and an instant preview.
bun run devEdit a file directly in GitHub
- Navigate to the desired file(s).
- Click the "Edit" button (pencil icon) at the top right of the file view.
- Make your changes and commit the changes.
Use GitHub Codespaces
- Navigate to the main page of your repository.
- Click on the "Code" button (green button) near the top right.
- Select the "Codespaces" tab.
- Click on "New codespace" to launch a new Codespace environment.
- Edit files directly within the Codespace and commit and push your changes once you're done.
This project is built with .
- Vite
- TypeScript
- React
- shadcn-ui
- Tailwind CSS
Run bun run verify before opening a PR or pushing if you want the same typecheck/lint/test/build gate that CI and the Husky pre-commit hook enforce.
Local development uses HTTPS only when the ignored local cert files are present. On machines without those files, Vite falls back to HTTP automatically, while deploy builds still upload Sentry source maps when SENTRY_AUTH_TOKEN is available through the deploy flow.
If you previously used the old custom .githooks path and Husky does not trigger, run git config --unset core.hooksPath once and then bun run prepare.
Production deploys run automatically on pushes to main via deploy-production.yml.
The canonical production URL is https://win3bitco.in. The deploy bucket name www.winabitco.in is an infrastructure detail, not the canonical URL for verifying what is live.
Production only reflects commits that exist on GitHub main. Local-only commits, detached worktrees, and unpublished SHAs are not eligible for production deploys.
To verify what is live in production, check the footer on https://win3bitco.in or inspect https://win3bitco.in/build-info.json.
The workflow uses the GitHub production environment and expects:
- Variable
AWS_REGION=us-east-2 - Variable
S3_BUCKET=www.winabitco.in - Variable
CLOUDFRONT_DISTRIBUTION_ID=EVH2SH6YOOO76 - Variable
AWS_DEPLOY_ROLE_ARN=<oidc-assumable-role-arn> - Secret
SENTRY_AUTH_TOKEN=<production sentry token>
For local manual deploys, use:
./scripts/build-and-deploy-to-s3.shOr, if the build already exists and you only want the deploy step:
bun run deployThe win3bitcoin.com redirect infrastructure is separate from the main app deploy and remains unchanged.
To have win3bitcoin.com redirect to the app, see S3 redirect setup (one-time bucket + DNS; use ./scripts/setup-redirect.sh as the orchestrator or call the step scripts directly under ./scripts/redirect/).
We don't support custom domains (yet). If you want to deploy your project under your own domain then we recommend using Netlify. Visit our docs for more details: Custom domains