Free tools Windows power users keep installed
One-click scans. No signup required.
The dependable way to self-host Reactive Resume is a Docker Compose stack on a Linux VPS: one Reactive Resume application container, one PostgreSQL service, persistent storage for uploads, and a reverse proxy that terminates HTTPS. The official minimum is 1 vCPU and 1 GB of RAM; allocate 2 GB when PostgreSQL runs on the same VPS. From version 5.1.0 onward, PDF creation runs in the browser, so a new installation does not need Browserless or the old printer variables.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What the deployment contains
Reactive Resume is deployed as an application and API service backed by PostgreSQL. The official image runs one application container that serves both the web interface and API. PostgreSQL should run as a separate Compose service on a private container network, with no database port exposed to the public internet.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchA production-ready layout has four logical parts:
- Reactive Resume application: serves the browser UI, API, authentication, resume data and PDF export.
- PostgreSQL: stores accounts, resume records, settings and other application data.
- Persistent file storage: a local directory such as
./data:/app/datawhen S3-compatible storage is disabled, or an S3-compatible bucket as an alternative. - Reverse proxy: accepts HTTPS on the public domain and forwards the complete application, including API requests, uploads, fonts and static assets, to the application container.
Keep the database and application on the same private Docker network. Only the reverse proxy needs to be reachable from the internet. If the proxy is installed directly on the VPS, publish the application only on a local interface or otherwise restrict its firewall access so visitors cannot bypass HTTPS.
“There is no difference in features between the cloud-hosted version and the self-hosted option,” according to the project quickstart.
#1 Best Overall
Sale
TOZO A1 Wireless Earbuds Bluetooth 5.3 Light Weight in Ear Headphones | IPX5 Waterproof,2 Mics for AI Calls,Immersive Premium Sound Bass Headset with Charging Case,32 EQ via App Black
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
VPS requirements and planning
CPU, memory and disk
| Resource | Official guidance | Practical interpretation |
|---|---|---|
| CPU | 1 vCPU minimum | Enough for a small, single-instance installation; additional capacity helps when several people edit or export at once. |
| RAM | 1 GB minimum | Use 2 GB when PostgreSQL is on the same host, which is the usual Compose arrangement. |
| Disk | Start with 10–20 GB for PostgreSQL and uploads | Increase the volume as accounts, uploaded assets and database backups grow. |
| Network | Public IP and a DNS name | Point a hostname such as resume.example.com to the VPS before requesting a certificate. |
The figures are starting points, not capacity guarantees. A single user with a few resumes consumes little CPU, while a shared service with many uploads, frequent exports and retained backups needs more memory and disk. Monitor free space and memory rather than assuming the initial allocation will remain sufficient.
Software prerequisites
- Linux VPS with administrative access, a public IP address and a firewall.
- Docker Engine 20.10 or newer.
- Docker Compose 2.0 or newer through the Compose plugin.
- A DNS record for the final hostname.
- A private place to keep the environment file and database credentials.
Install Docker from the instructions for your Linux distribution, then verify both components before creating the application:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →docker --version
docker compose versionThe reported versions must meet the minimums above. If docker compose is not recognized, install the Compose plugin rather than relying on an obsolete standalone command.
Choose storage and database boundaries first
PostgreSQL on the VPS
Running PostgreSQL as a Compose service keeps the deployment self-contained and avoids a public database endpoint. Set the application’s DATABASE_URL to the PostgreSQL service name (or another address reachable from the application container), not to localhost. Inside a container, localhost means that same container, not the database service.
Do not publish PostgreSQL’s port in Compose and do not open it in the VPS firewall. The application reaches it over the private Docker network; internet clients do not.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Local uploads or S3-compatible storage
With S3 disabled, mount a persistent host directory into the application’s data path, for example ./data:/app/data. This keeps uploads when the application container is recreated. Without that mount, files stored only in the container’s writable layer can disappear during replacement.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →S3-compatible storage is an alternative when you want object storage outside the VPS or need a storage layer that can be shared by multiple application instances. Whichever option you choose, include it in your backup and restoration plan. A PostgreSQL dump alone does not restore files stored in the data directory, and copying uploads alone does not restore the records that reference them.
Create the Compose project
1. Prepare a dedicated directory
Use a directory owned by an administrator and protect it from ordinary users:
mkdir -p ~/reactive-resume/data
cd ~/reactive-resume
chmod 700 .
Place the project’s compose.yml in this directory. Start from the current Compose example in the Reactive Resume self-hosting documentation so image names, service settings and volume declarations match the release you intend to run. The published application image is available as amruthpillai/reactive-resume:latest; the project also publishes an image through GitHub Container Registry.
2. Create a private environment file
Create .env beside compose.yml and set the public origin, database connection and authentication secret:
Recommended Free Tools
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
APP_URL=https://resume.example.com
DATABASE_URL=<postgresql-connection-using-the-compose-service-name>
AUTH_SECRET=<long-random-secret>
Set APP_URL to the final public HTTPS origin, including the correct scheme and hostname. Do not use an internal container address or a temporary HTTP URL if users will access the service through HTTPS. The value is used when Reactive Resume builds links and handles browser-origin checks.
Generate AUTH_SECRET on the VPS instead of inventing a memorable phrase:
openssl rand -hex 32Copy the output into .env, restrict the file, and never commit it to a repository or paste it into a public support thread:
chmod 600 .envUse the PostgreSQL service name and the credentials defined by your Compose configuration in DATABASE_URL. Keep the complete connection string private. If you change the database password later, update the environment file and the database consistently.
3. Keep obsolete PDF variables out of new deployments
Reactive Resume 5.1.0 and later generate PDFs entirely client-side with @react-pdf/renderer. Remove old PRINTER_* and BROWSERLESS_* variables when creating a new stack. They belong to older server-side PDF arrangements and can cause confusion during troubleshooting. Existing installations should check the release notes and remove those settings as part of a controlled upgrade rather than deleting configuration blindly.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Start the services safely
- Review
compose.ymland confirm that the application and PostgreSQL share a private network, the data directory is mounted persistently, and PostgreSQL has no public port mapping. - From the project directory, pull the images and start the stack in detached mode:
docker compose pull
docker compose up -d- Watch the application log while the first boot completes:
docker compose logs -f reactive-resumeOn every start, the server runs database migrations before serving traffic. The first launch therefore may take longer than later restarts. Wait for PostgreSQL to become reachable, migrations to finish and the application health check to report success before placing the service behind a public hostname.
- From the VPS or an allowed network context, check the health endpoint:
curl http://127.0.0.1:3000/api/healthThe endpoint should return a successful health response. If your proxy or Compose file uses a different local binding, query the address and port actually exposed on the host; the documented health check uses 127.0.0.1:3000.
Put the complete application behind HTTPS
Configure a reverse proxy for the DNS name and obtain a certificate through the proxy’s normal certificate workflow. The proxy must forward more than the HTML page. Route the API, upload requests, fonts, JavaScript, stylesheets, images and other assets to the same Reactive Resume application service. Proxying only the landing page commonly produces a screen that loads but cannot log in, save a resume or upload a file.
Use the public HTTPS address in APP_URL. Redirect plain HTTP to HTTPS, preserve the original host and scheme headers, and allow request bodies large enough for the uploads your users need. Keep the application’s direct port private so clients cannot reach an alternate, non-TLS origin.
Proxy validation checklist
- Open the hostname in a private browser window and confirm the certificate is valid.
- Create an account or sign in, then refresh the page to test the session cookie.
- Create and edit a resume, including a field that saves through the API.
- Upload an image or other supported asset and reload the editor.
- Open a public resume link if you use sharing.
- Export a PDF and verify that fonts, icons and page breaks appear correctly.
These tests exercise the paths most likely to be broken by an incomplete proxy configuration. A successful health endpoint alone does not prove that browser-origin settings, uploads or public sharing work through the final domain.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Backups and persistence
Back up PostgreSQL and the uploaded-file store on separate schedules appropriate to the data’s value. Store at least one copy outside the VPS so a disk failure or deleted server does not remove both the service and its backup.
- Database backup: create regular PostgreSQL dumps or use an equivalent backup method for the database service.
- File backup: copy the mounted
datadirectory when local storage is enabled, or use the object-storage provider’s versioning and backup controls when S3-compatible storage is enabled. - Secret backup: keep a protected copy of
.envand the deployment notes needed to recreate the stack. TreatAUTH_SECRETas sensitive. - Restore test: periodically restore the database and files into an isolated Compose project, then sign in and open an uploaded resume.
A backup is only useful if it can be restored. Test the relationship between database rows and uploaded files; restoring one without the other can leave resumes that reference missing assets.
Routine updates without avoidable downtime
- Read the release notes for the target version and check for migration or configuration changes.
- Take a fresh PostgreSQL backup and back up local uploads or confirm the object-storage backup is current.
- Pull the published image. You can use
amruthpillai/reactive-resume:latestor the project’s GitHub Container Registry image, according to your chosen Compose file. - Recreate the application service with Compose:
docker compose pull
docker compose up -d- Follow the logs through migrations, check the health endpoint, and repeat the browser tests for login, editing, upload, sharing and PDF export.
Keep the previous image reference and a known-good database backup until the new release has passed these checks. If a migration fails, stop exposing the service, inspect the error and restore according to your tested procedure rather than repeatedly restarting a broken container.
Scaling beyond one application container
A single application instance is the simplest arrangement and supports the core resume features without Redis. When you run multiple application instances, the project documentation requires shared Redis and a deployment namespace for rate limits, resumable streams, cancellation, notifications and view deduplication. Those shared services must be designed before adding replicas; simply starting a second container can produce inconsistent sessions or background behavior.
Scaling also changes storage decisions. Local disk mounted separately into each instance is not automatically shared, so use shared S3-compatible storage or another deliberately shared filesystem for uploads. Keep PostgreSQL reachable by every application instance over a private network and ensure all instances use the same relevant secrets and public URL.
Troubleshooting common failures
| Symptom | Likely cause | Action |
|---|---|---|
| Application container exits during startup | Migration failure, malformed DATABASE_URL or database connectivity problem |
Run docker compose logs -f reactive-resume; verify the PostgreSQL service name, credentials, network and database readiness before restarting. |
| Health endpoint is unavailable | Container is still starting, has failed its health check, or the host binding differs from the documented address | Inspect docker compose ps and logs, then query the actual local port. Do not expose the service publicly until health is stable. |
| Uploads disappear after a recreate | The application data directory was not mounted persistently | Configure a host mount such as ./data:/app/data or use S3-compatible storage, then restore any recoverable files from backup. |
| Login works locally but fails through the domain | APP_URL does not match the public HTTPS origin, or the proxy is not preserving host/scheme information |
Correct APP_URL, reload the stack and verify the proxy’s forwarded headers and HTTPS redirect. |
| The page loads but saving or uploading fails | Only the frontend path was proxied, or request bodies are restricted | Forward the API and upload paths to the same application service and raise the proxy’s body-size limit as needed. |
| PDF export fails after an old upgrade | Legacy printer or Browserless variables remain, or the browser cannot load required assets | For version 5.1.0 and later, remove obsolete PRINTER_* and BROWSERLESS_* settings and retest through the HTTPS domain. |
| Database is reachable from the internet | A PostgreSQL port mapping or firewall rule was added unnecessarily | Remove the public mapping, restrict the firewall and keep database traffic on the private Compose network. |
Deployment choices worth deciding explicitly
| Decision | Simpler option | When the alternative is justified |
|---|---|---|
| Database location | PostgreSQL Compose service on the VPS | A managed PostgreSQL service can reduce database administration, but adds an external dependency and network configuration. |
| Upload storage | Persistent local data directory |
S3-compatible storage is preferable when files must survive host replacement independently or be shared by several instances. |
| Application count | One application container | Multiple instances require shared Redis, a deployment namespace and shared file storage. |
| Proxy placement | Reverse proxy on the same VPS | An external proxy or load balancer can centralize certificates, but introduces another service to secure and monitor. |
| Administration | Run Compose locally on the VPS | Docker Compose also supports targeting a remote Docker host with DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH; use that only with controlled TLS credentials and restricted administrative access. |
There is no single best choice for every operator. The important boundary is that database access, secrets and file persistence remain intentional, documented and recoverable. A small personal server benefits from fewer moving parts; a shared service benefits from managed backups, external object storage and tested scaling components.
Security and operations checklist
- Apply operating-system security updates and allow only required firewall ports, normally SSH and HTTPS.
- Use key-based SSH administration and disable unnecessary login methods.
- Keep
.env, database credentials andAUTH_SECRETout of source control and world-readable directories. - Do not publish PostgreSQL’s port or the application’s unencrypted port to the public internet.
- Renew the TLS certificate automatically and monitor expiry.
- Watch disk usage for PostgreSQL, uploads, Docker layers and backups.
- Review Compose logs after restarts and upgrades; retain enough history to diagnose migration failures.
- Schedule database and upload backups, keep an off-host copy and perform restoration tests.
- Record the image tag, environment values, DNS name, backup location and recovery steps in a protected runbook.
- For a multi-instance deployment, provision shared Redis and shared upload storage before adding replicas.
When the VPS is ready for users
The installation is ready when the application remains healthy after a restart, the public hostname serves valid HTTPS, and the complete user journey works through the proxy: registration, login, editing, saving, uploading, sharing and client-side PDF export. Confirm that a restored backup can recreate both database records and uploaded files before treating the service as production-ready.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
