Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →The reliable path is to provision a Linux VPS, secure SSH access with a key and a non-root sudo account, connect with VS Code’s Remote-SSH extension, install your application’s runtime on the server, and place Nginx and HTTPS in front of the running process. For repeated releases, you can instead build locally and synchronize the result with rsync. The right choice depends on where you want dependencies, builds, debugging, and rollback to happen.
What a VS Code-to-VPS deployment actually does
A VPS is a Linux virtual machine that you administer over the network. Your website’s files, dependencies, build tools, application process, web server, and certificates ultimately live on that machine. VS Code is the working interface; it is not the production server itself.
As an Amazon Associate I earn from qualifying purchases.
There are two practical deployment patterns:
- Remote-SSH editing: VS Code opens a folder on the VPS. The integrated terminal, language tools, extensions, dependency installation, builds, and debugging run on the VPS.
- Local build plus synchronization: you develop and build on your computer, then copy the output and any required server files to the VPS, usually with
rsync.
Both patterns can use the same production layer: an application listening on a private port, Nginx accepting public HTTP/HTTPS traffic, and a process strategy that restarts the application after a crash or reboot.
Choose the server and prepare the prerequisites
Provision a supported Linux VPS
Choose a current Linux distribution. DigitalOcean’s production guidance recommends a current Ubuntu LTS image for a new setup and defines a Droplet as a Linux-based virtual machine. Select enough memory and CPU for the framework, build, database, and traffic you expect. Visual Studio Code lists 1 GB RAM as a minimum for a remote host and recommends 2 GB RAM with a two-core CPU; those are vendor requirements, not an independent performance benchmark.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Record the server’s public IP address, its initial hostname, and the SSH port if it is not the default port 22. Point your domain’s DNS records at the VPS before requesting a certificate. Keep the provider’s recovery console available in case a firewall or SSH change locks you out.
Install the client-side tools
- VS Code on your local computer.
- The Microsoft Remote – SSH extension if you want to edit remotely.
- An OpenSSH client. In a terminal, verify it with
ssh -V. rsyncif you will synchronize files from a Unix-like local system. On Windows, use a compatible environment that provides OpenSSH and rsync, or use Remote-SSH instead.
Meet the remote-host requirements
The Remote-SSH extension connects to a machine running an SSH server and installs VS Code Server there. VS Code identifies Bash, tar, and either curl or wget among typical remote prerequisites. If the extension reports that it cannot install its server component, check those utilities first, then check outbound network access and available disk space.
Free tools Windows power users keep installed
One-click scans. No signup required.
Secure SSH access before opening VS Code
Do the initial hardening from the provider console or a temporary administrative session. The production baseline described by DigitalOcean’s setup guidance is key-based authentication, a non-root account with sudo access, password-login disabled, and firewall controls.
- Create or select an SSH key pair. Keep the private key only on your computer and add the public key to the VPS account through the provider’s console. Never paste the private key into the server or commit it to your repository.
- Create a deployment account. Use a name such as
deploy, grant it sudo rights, and use that account for normal administration. Reserve root for recovery tasks. - Test the account before changing SSH policy. From a second terminal, run
ssh deploy@your-server-ip. Do not close your original administrative session until this succeeds. - Apply a firewall policy. Allow SSH, HTTP, and HTTPS. With a UFW-based Ubuntu setup, the conceptual rules are
sudo ufw allow OpenSSH,sudo ufw allow 80/tcp, andsudo ufw allow 443/tcp, followed by enabling UFW only after confirming the SSH rule. - Disable password authentication after key login works. In
/etc/ssh/sshd_config, setPasswordAuthentication no, validate the configuration if your distribution provides an SSHD test command, and restart the SSH service. Keep an existing session open and test a new key-based login immediately.
Avoid exposing your application port publicly. If the app listens on port 3000, 8000, or another framework default, bind it to 127.0.0.1 and let Nginx be the only public application entry point.
Verify the terminal connection, then connect Remote-SSH
Confirm plain SSH first
Use the same identity and hostname that you will give VS Code:
ssh -i ~/.ssh/id_ed25519 deploy@your-domain-or-ipIf your key is loaded into your SSH agent or is in the default location, the -i option may be unnecessary. Once connected, check the remote identity and operating system:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
whoami
uname -a
pwdThese commands should show the non-root account and the VPS filesystem, not your local computer.
Open the VPS in VS Code
- Install and enable Remote – SSH.
- Open the Command Palette with
Ctrl+Shift+Pon Windows/Linux orCmd+Shift+Pon macOS. - Run Remote-SSH: Connect to Host….
- Choose an existing SSH host or enter the same identity, such as
deploy@your-domain-or-ip. If you use a non-default key, define it in your local SSH configuration and select that host. - Accept the host key when you have verified the server identity. VS Code connects, then installs VS Code Server on the remote operating system.
- Use File > Open Folder… and select the application directory on the VPS.
The bottom-left status indicator should show an SSH connection. Open the integrated terminal and run pwd and node --version (or the equivalent runtime command). The result is from the VPS. Extensions that run remotely, terminal commands, package installation, and debugging therefore use the server’s CPU, memory, filesystem, and network.
Remote-SSH versus local build plus rsync
| Decision | Remote-SSH editing | Local build plus rsync |
|---|---|---|
| Where dependencies install | On the VPS, inside the remote project directory. | On the local machine for the build; production dependencies must still be installed or supplied on the VPS when the server runs the app. |
| Large or repeated transfers | Opening and editing files does not require copying the whole tree, but remote builds consume VPS resources. | rsync transfers only changed files after the first copy and is the better fit for large trees copied repeatedly. |
| Build reproducibility | Builds use the VPS operating system, runtime, lockfile, and installed tools, reducing “works locally” differences. | Builds are fast and convenient locally, but you must pin runtime and dependency versions and ensure the server receives exactly the intended output. |
| Debugging location | Breakpoints and logs run beside the production-like process on the VPS. | Local debugging is faster and safer; remote-only failures require a separate server test or log session. |
| Rollback method | Use version control or release directories on the VPS before switching the active path. | Keep previous build artifacts locally and synchronize a known-good artifact back to the server. |
| Best use | Small teams, server-side applications, and situations where the VPS should be the authoritative workspace. | Static sites, large front-end builds, and teams that require a repeatable local build pipeline. |
VS Code also documents SSHFS for convenient individual-file access and rsync for bulk file operations. SSHFS is useful for browsing or changing a few files; it is not a substitute for a deliberate release process when many files change.
Workflow A: deploy by working directly on the VPS
1. Put the project in a stable server directory
Create a directory owned by the deployment account, such as /var/www/example-app, and open that directory through Remote-SSH. Keep secrets outside the repository or provide them through the process environment. Do not upload a local .env file containing production credentials unless you have intentionally secured its permissions.
Recommended Free Tools
2. Install the framework’s runtime
Install the runtime version required by the project, then verify it in the VS Code terminal. For a Node.js project, the official VS Code tutorial demonstrates starting an Express application remotely with npm start. A Python, PHP, Ruby, Go, or other stack has its own package manager, virtual environment, build command, and start command; use the project’s documented entry point rather than assuming npm start applies.
3. Install locked dependencies and build
Use the lockfile-aware command for your package manager, run the project’s build script if it has one, and inspect the generated directory before publishing it. For Node projects this commonly means a clean install based on package-lock.json, followed by the repository’s build script. Keep development dependencies out of a production-only installation when the framework permits it.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
4. Test privately before exposing the app
Start the app on a loopback address and test it from the VPS:
curl -I http://127.0.0.1:3000Replace port 3000 with the port your application actually uses. A successful local response proves that the runtime and process are working, but it does not yet prove DNS, Nginx, firewall, or HTTPS configuration.
Workflow B: build locally and synchronize with rsync
1. Build and verify on your computer
Install dependencies from the lockfile, run tests and the production build, and identify the exact files needed by the server. For a static site, that may be only the generated dist or build directory. For a server application, include the application files, lockfile, configuration templates, and any production assets, but exclude local caches and source-control metadata unless the server needs them.
2. Perform a dry run
A dry run shows what would change without modifying the VPS:
rsync -avzn --delete
--exclude '.git'
--exclude 'node_modules'
./dist/ deploy@your-server:/var/www/example-app/The trailing slash on ./dist/ means “copy the contents of this directory.” Review the file list carefully. The --delete option removes remote files that no longer exist locally; it keeps deployments clean but can destroy manually uploaded files in the destination.
3. Synchronize the approved release
rsync -avz --delete
--exclude '.git'
--exclude 'node_modules'
./dist/ deploy@your-server:/var/www/example-app/For a server-side app, synchronize to a versioned release directory rather than overwriting the live directory, install or verify production dependencies there, run a local loopback test, and switch Nginx or the service to that release. This creates a concrete previous directory for rollback.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Run the application as a service
A terminal command is suitable for a test, not for a production process that must survive logout and reboot. Use the service mechanism appropriate to your operating system and framework. On a systemd-based Linux VPS, a unit normally specifies the non-root user, working directory, environment, start command, restart policy, and dependency on the network.
[Unit]
Description=Example web application
After=network.target
[Service]
User=deploy
WorkingDirectory=/var/www/example-app
Environment=NODE_ENV=production
ExecStart=/usr/bin/npm start
Restart=on-failure
[Install]
WantedBy=multi-user.targetSave a unit under the system’s service directory, reload systemd, enable it at boot, and start it. Then inspect status and logs before configuring Nginx:
sudo systemctl daemon-reload
sudo systemctl enable --now example-app
sudo systemctl status example-app
sudo journalctl -u example-app -n 100 --no-pagerAdjust ExecStart, the runtime path, user, and working directory to your project. If the service starts but exits immediately, run the same command as the service user and check environment variables, file permissions, and the application’s bind address.
Put Nginx in front of the application
Nginx can serve a static build directly or reverse-proxy requests to an application listening on localhost. These are separate deployment concerns: a healthy application process does not configure Nginx automatically.
Reverse proxy example
server {
listen 80;
server_name example.com www.example.com;
location / {
proxy_pass http://127.0.0.1:3000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}Replace the domain and port. The application should listen on loopback; Nginx is the public listener.
Static-site server block
server {
listen 80;
server_name example.com www.example.com;
root /var/www/example-app;
index index.html;
location / {
try_files $uri $uri/ /index.html;
}
}Use the fallback only when the front-end router requires it. If the generated site has a different entry file or directory, change root and index accordingly.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Validate before reloading
- Place the server block in the distribution’s enabled-sites configuration and ensure the path is enabled according to that distribution’s layout.
- Run
sudo nginx -t. Do not reload if the test reports a syntax or file error. - Reload Nginx with systemd, for example
sudo systemctl reload nginx. - Request the site over HTTP and inspect Nginx’s error log if the response is not what you expect.
Add HTTPS with Certbot and test renewal
After DNS resolves to the VPS and Nginx serves the correct domain, use Certbot to request a certificate and configure HTTPS. The exact package installation command depends on the Linux distribution, but the operational sequence is consistent: issue the certificate, verify the HTTPS virtual host, and test automated renewal.
- Confirm that ports 80 and 443 are allowed through both the VPS firewall and any provider-level firewall.
- Run Certbot with the Nginx integration for each hostname you serve, following the prompts to redirect HTTP to HTTPS if that matches your application’s requirements.
- Open the HTTPS URL and check the certificate hostname and the application response.
- Run
sudo certbot renew --dry-run. A successful dry run demonstrates that the renewal configuration can complete without waiting for the certificate’s actual renewal window.
Renewal is independent of your application deployment. Updating the app should not overwrite Nginx’s certificate configuration, and renewing a certificate should not require rebuilding the app.
Release, rollback, and maintenance practices
Use an identifiable release
Tag releases in version control or name synchronized directories with a commit identifier and date. Keep the currently active release separate from the incoming release. This prevents a half-copied tree from becoming the version users see.
Switch only after verification
Install dependencies and run a loopback health check in the new release. Reload or restart the service only after that check passes. Then request the public URL through Nginx and inspect application and web-server logs.
Rollback the smallest possible unit
If the new release fails, stop or restart the service against the previous directory, or synchronize the last known-good artifact again. Do not use rsync --delete against a directory that contains uploads, certificates, or other data not represented in your build output.
Outdated 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 matchPC 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 & 11Patch the host deliberately
Keep the operating system, runtime, Nginx, Certbot, and application dependencies maintained. Apply updates in a maintenance window, confirm that SSH still works, and check the service status and HTTPS endpoint afterward.
Self-managed VPS versus managed hosting
| Factor | Self-managed VPS | Managed hosting |
|---|---|---|
| Server maintenance | You patch the operating system, configure SSH and firewalls, maintain Nginx, renew certificates, and troubleshoot services. | The provider handles more of the operating system and platform maintenance, reducing routine administration. |
| SSH and root access | Typically provides direct SSH and substantial control, subject to the provider’s policies. | May limit root access or abstract server configuration; verify the exact access model before choosing. |
| Nginx and runtime control | You choose Nginx configuration, runtime versions, service units, ports, and deployment layout. | Common runtimes and web-server settings may be available through a control panel, while low-level customization can be restricted. |
| Scaling controls | You select the VPS size and design your own horizontal scaling, load balancing, backups, and monitoring. | Scaling and backups may be integrated, but the available controls and limits depend on the plan. |
| Total cost | Often a lower direct infrastructure bill, but your time and operational risk are part of the real cost. | Usually costs more for the managed layer, which can be worthwhile when SSH and server administration are not your team’s strength. |
DigitalOcean’s production setup guidance names Cloudways as a managed alternative for readers who struggle with SSH and server management. Compare the actual access, runtime, backup, scaling, and regional terms of any service before committing.
Troubleshooting the common failure points
| Symptom | Likely cause | What to check |
|---|---|---|
| Remote-SSH connects, then fails while installing VS Code Server | Missing Bash, tar, curl/wget, insufficient memory, disk space, or blocked outbound access. |
Run command -v bash tar curl wget, check memory and disk, and read the Remote-SSH output panel. |
| SSH says “Permission denied” | Wrong user, wrong private key, missing public key, or restrictive key-file permissions. | Repeat the working terminal command with -i, verify the username, and test the key before changing server policy. |
| SSH worked until the firewall was enabled | The SSH rule was omitted or applied to the wrong port. | Use the provider console, restore the SSH allow rule, and keep a second session open while testing. |
| The app works on localhost but not in a browser | Nginx points to the wrong port, the app is bound incorrectly, DNS is wrong, or a firewall blocks 80/443. | Test the app with curl on the VPS, run nginx -t, inspect the server block, and verify DNS and firewall rules. |
| Nginx returns 502 Bad Gateway | The application service is stopped, crashed, listening on another port, or bound to an unusable address. | Check systemctl status, journalctl, the Nginx error log, and the local upstream request. |
| HTTPS issuance fails | The domain does not resolve to this VPS, port 80/443 is blocked, or Nginx serves a different hostname. | Verify DNS from outside the server, confirm firewall rules, validate Nginx, and retry Certbot only after HTTP works. |
| A deployment removed an uploaded file | rsync --delete mirrored a build directory over a directory containing unmanaged data. |
Separate uploads and persistent data from release artifacts, and use a dry run before every destructive synchronization. |
Production deployment checklist
- Current Linux image selected and VPS resources match the application.
- SSH key installed; non-root sudo account tested in a second session.
- Password-based SSH login disabled only after key login succeeds.
- Firewall allows SSH, HTTP, and HTTPS, but not the private application port.
- Remote-SSH prerequisites—Bash,
tar, andcurlorwget—are present. - Dependencies installed from the project’s lockfile and the production build verified.
- Application runs under a service strategy and restarts appropriately.
- Nginx configuration passes
nginx -tbefore reload. - Domain resolves to the VPS and Certbot has issued the certificate.
certbot renew --dry-runsucceeds.- Release artifacts and persistent data are separated, with a tested rollback path.
The practical decision
Use Remote-SSH when you want the VPS to be the execution environment and need to inspect, run, and debug the site where it will live. Use local builds plus rsync when transfer efficiency, local build speed, and repeatable artifacts matter more. In either case, treat SSH hardening, a supervised application process, Nginx validation, and certificate renewal as separate steps. That separation makes failures easier to diagnose and gives you a deployment you can repeat without turning a successful local edit into an untracked production change.
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.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →
