Skip to main content

​
Options

Reactive Resume offers flexibility in how you want to use it. Choose the option that best fits your needs:

Use the Cloud Version

The fastest way to get started. Recommended for most users.

Self-Host with Docker

Deploy your own instance with complete control. Requires some technical knowledge.

​
Using the Cloud Version

The easiest way to use Reactive Resume is through our cloud version at rxresu.me. This service is completely free and will always remain free.
1

Create an Account

Visit rxresu.me and sign up for free using your email, or sign in with your GitHub or Google account.
2

Create Your First Resume

Click the Create Resume button on your dashboard. Give your resume a name and select a template to get started.
3

Fill in Your Details

Use our intuitive builder to add your:
  • Personal information
  • Work experience
  • Education
  • Skills
  • Projects
  • And more…
4

Export & Share

When you’re ready, export your resume as a PDF or share it via a unique public link.
Your resume updates in real-time as you type. The preview panel shows exactly how your final PDF will look.

​
Self-Host with Docker

For users who prefer complete control over their data, you can deploy Reactive Resume on your own infrastructure using Docker.

​
Prerequisites

Before you begin, ensure you have the following installed:
There is no difference in features between the cloud-hosted version and the self-hosted option. Both provide the same privacy, customization, and functionality. Choose whichever deployment type suits your needs!

​
Quick Deployment

1

Clone the Repository

git clone https://github.com/amruthpillai/reactive-resume.git
cd Reactive-Resume
2

Configure Environment Variables

Create a .env file in the root directory with the following variables:
# Application
APP_URL=http://localhost:3000

# Database
DATABASE_URL=postgresql://postgres:postgres@postgres:5432/postgres

# Authentication (generate a secure secret)
AUTH_SECRET=your-secure-secret-key-here

# Storage (S3-compatible)
S3_ACCESS_KEY_ID=seaweedfs
S3_SECRET_ACCESS_KEY=seaweedfs
S3_ENDPOINT=http://seaweedfs:8333
S3_BUCKET=reactive-resume
S3_FORCE_PATH_STYLE=true
For production deployments, always use strong, unique values for AUTH_SECRET and database credentials.
3

Start the Services

docker compose up -d
This will start:
  • PostgreSQL — Database for storing user data and resumes
  • SeaweedFS — S3-compatible storage for file uploads
  • Printer — PDF and screenshot generation service (browserless/chromium)
  • Reactive Resume — The main application
4

Access Your Instance

Once all services are running, access your Reactive Resume instance at:
http://localhost:3000

​
Docker Compose Services

Here’s what each service in the stack does:
ServicePortDescription
postgres5432PostgreSQL database for storing all application data
seaweedfs8333S3-compatible object storage for file uploads
printer4000Headless Chromium service for PDF and screenshot generation
app3000The main Reactive Resume application

​
Health Checks

All services include built-in health checks. You can verify everything is running correctly: 
docker compose ps
You should see all services with a healthy status.

​
Environment Variables Reference

Here’s a complete list of environment variables you can configure:

​
Required Variables

VariableDescriptionExample
DATABASE_URLPostgreSQL connection stringpostgresql://user:pass@host:5432/db
AUTH_SECRETSecret key for authenticationGenerate with openssl rand -base64 32
APP_URLPublic URL of your Applicationhttps://rxresu.me
PRINTER_ENDPOINTURL of the printer servicehttp://printer:3000

​
Optional Variables

VariableDescriptionDefault
PRINTER_APP_URLPublic URL for the printer to access the Application—
GOOGLE_CLIENT_IDGoogle OAuth Client ID—
GOOGLE_CLIENT_SECRETGoogle OAuth Client Secret—
GITHUB_CLIENT_IDGitHub OAuth Client ID—
GITHUB_CLIENT_SECRETGitHub OAuth Client Secret—
OAUTH_PROVIDER_NAMECustom OAuth Provider Name—
OAUTH_CLIENT_IDCustom OAuth Client ID—
OAUTH_CLIENT_SECRETCustom OAuth Client Secret—
OAUTH_DISCOVERY_URLOIDC Discovery URL (use this OR manual URLs below)—
OAUTH_AUTHORIZATION_URLOAuth Authorization URL (manual config)—
OAUTH_TOKEN_URLOAuth Token URL (manual config)—
OAUTH_USER_INFO_URLOAuth User Info URL (manual config)—
OAUTH_SCOPESOAuth Scopes (space-separated)openid profile email
SMTP_HOSTSMTP Server Host (for email features)—
SMTP_PORTSMTP Server Port587
SMTP_USERSMTP Username—
SMTP_PASSSMTP Password—
SMTP_FROMDefault FROM address for emails—
SMTP_SECUREUse secure SMTP connection (true or false)false
S3_ACCESS_KEY_IDS3 Access Key—
S3_SECRET_ACCESS_KEYS3 Secret Key—
S3_REGIONS3 Regionus-east-1
S3_ENDPOINTS3-compatible Endpoint URL—
S3_BUCKETS3 Bucket Name—
S3_FORCE_PATH_STYLEUse path-style URLs for S3 (set true for MinIO/SeaweedFS)false
FLAG_DEBUG_PRINTERUsed for debugging the printer routefalse
FLAG_DISABLE_SIGNUPSDisables new user signupsfalse
FLAG_DISABLE_EMAIL_AUTHDisables email/password login (SSO only)false
Note: Some variables are only required for using related features (OAuth, SMTP, S3, etc.) and can be left unset if unused.
Hybrid Setup Note: The PRINTER_APP_URL variable is required when running Reactive Resume outside of Docker while the printer service is running inside Docker. In this scenario, the printer needs to reach your local app to render resumes for PDF generation. Since Docker containers cannot access localhost on your host machine directly, you must set PRINTER_APP_URL to http://host.docker.internal:3000. This special hostname allows Docker containers to communicate with services running on your host machine.
Alternative Printer Options: If you don’t want to use browserless, you can use any headless Chrome/Chromium instance with its remote debugging port open. For example, run chromium --remote-debugging-port=9222 and point PRINTER_ENDPOINT to that instance.

​
Next Steps

Development Setup

Set up a development environment to contribute or customize Reactive Resume.

Project Architecture

Learn about the project structure and architecture.
Having trouble? Check our GitHub Issues or reach out via email.