Skip to main content
You have two ways to start using File Transfer Pavan. The fastest is to open the live app at https://file-share-05.lovable.app; no setup is required. If you want to customize the codebase or run your own instance, follow the steps below to clone the repository, configure your environment, and launch the local dev server.

Prerequisites

Before you begin, make sure you have the following ready.
  • Node.js 18 or newer installed on your machine
  • A Supabase project with a database and Storage bucket configured
  • A modern browser that supports Progressive Web App installation (Chrome, Edge, Firefox, or Safari)

Steps

1

Clone the repository

Run the following command to download the source code and enter the project directory.
2

Install dependencies

Choose your preferred package manager and install the project dependencies.
3

Create environment variables

Create a .env.local file in the project root and add your Supabase credentials.
Replace the placeholder values with the URL and keys from your Supabase project settings.
4

Start the dev server

Run the development command for your package manager.
The dev server starts on http://localhost:8080.
5

Open the app

Navigate to http://localhost:8080 in your browser. You should see the landing page and be able to sign up or log in.

Available scripts

Production build

When you are ready to deploy, generate a production build and preview it locally to confirm everything works.
npm run build outputs an optimized bundle with code splitting enabled. npm run preview starts a local static server so you can test the production artifacts before deploying.

Deploy to Vercel

You can deploy File Transfer Pavan to Vercel with a few CLI commands.
After the first deploy, add the required environment variables through the Vercel CLI or the project dashboard. Vercel will rebuild and redeploy automatically.

Run with Docker

A Dockerfile is included if you prefer a containerized deployment.
The container exposes port 8080, matching the default dev server port.
The development server runs on port 8080, not 3000. Make sure no other service is occupying that port before you start the app.