Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →ShipitJS can turn an SSH-accessible VPS deployment into a repeatable command: npx shipit production deploy. It creates a release from a chosen Git revision, switches a current symlink, retains older releases, and can run your application’s install, build, migration, reload, and health-check tasks. Shipit is the orchestration layer; it is not Node.js and it does not keep a Node process alive after deployment.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The reliable setup is therefore two parts: configure ShipitJS for secure, atomic file releases, then connect its task and event system to the process manager and operational checks your application needs.
As an Amazon Associate I earn from qualifying purchases.
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 →What ShipitJS does in a Node.js VPS deployment
The ShipitJS project describes Shipit as “an automation engine and a deployment tool.” In practical terms, it coordinates JavaScript tasks and SSH operations from your deployment machine. It can connect to one or more servers, obtain a Git revision, create a new release directory, copy the application, update a symlink, remove old releases, and emit lifecycle events for application-specific work.
ShipitJS does not replace the Node.js runtime, a reverse proxy, a database, or a process supervisor. After a release, something else must start and supervise your Node process, such as a systemd service or another process manager. Your Shipit tasks should reload that service only after the new release has passed installation and build checks.
#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.
The deployment boundary
- Shipit: SSH connections, release orchestration, Git checkout or transfer, symlink switching, retention, rollback, and task hooks.
- Node.js: executes your application.
- Process supervisor: restarts the application after a crash or reboot and performs a controlled reload.
- VPS services: normally include the operating system, SSH daemon, firewall, TLS or reverse proxy, database, logging, and backups.
Prerequisites for a production VPS
Prepare the server and deployment workstation before writing the Shipit file. The examples use a non-root account named deploy and an application directory at /var/apps/my-node-app; substitute paths that match your host.
On the VPS
- A supported Linux installation with Node.js and the package manager required by your project.
- An SSH account dedicated to deployments. Do not run routine releases as root.
- Write permission for the deployment root and permission to reload only the application service.
- Git access if the server will fetch the repository, or the SSH and HTTPS credentials needed by your selected repository URL.
- Enough disk space for the configured number of retained releases, temporary work, dependencies, and logs.
- A process supervisor and an HTTP endpoint that can be used for a post-deploy health check.
On the deployment machine
- Node.js and npm.
- Network access to the VPS over SSH.
- An SSH private key whose public key is authorized for the deploy account.
- Permission to read the Git repository and, when required, its submodules or private dependencies.
Keep private keys, repository tokens, database passwords, and application secrets out of the repository. Put runtime secrets in the VPS environment, a protected shared file, or a secret-management system, and grant the deploy account only the permissions it needs.
Install Shipit and create the production configuration
Install both the command-line interface and deployment plugin as development dependencies in the project that will run deployments:
npm install --save-dev shipit-cli
npm install --save-dev shipit-deployCreate shipitfile.js in that project. This minimal production configuration follows the documented ShipitJS pattern:
module.exports = shipit => {
require('shipit-deploy')(shipit)
shipit.initConfig({
default: {
deployTo: '/var/apps/my-node-app',
repositoryUrl: 'https://github.com/example/my-node-app.git',
key: '/home/deploy/.ssh/id_ed25519',
keepReleases: 5,
shallowClone: true
},
production: {
servers: '[email protected]'
}
})
}Replace the example repository and host with your values. The servers value accepts the user@host shorthand. Shipit also accepts a structured server object when you need a non-default SSH port or additional SSH options.
Configuration fields that matter
| Setting | Purpose | Production decision |
|---|---|---|
deployTo |
Remote deployment root. | Use a dedicated directory such as /var/apps/my-node-app, owned or writable by the deploy account. |
repositoryUrl |
Git source for the release. | Use HTTPS or git+ssh and ensure the fetching identity can read it. |
servers |
Remote deployment target. | Use a dedicated account; specify host, user, port, and SSH options explicitly when shorthand is insufficient. |
key |
Private SSH key used for the connection. | Point to a key readable only by the deployment user and protect it with normal filesystem permissions. |
keepReleases |
Number of old releases retained. | Choose a value that leaves rollback options without exhausting disk capacity. The example retains five. |
shallowClone |
Whether the documented deployment uses a shallow Git checkout. | The documented configuration sets it to true; use a full history only when your build or rollback process requires it. |
Select a revision deliberately
Do not allow an accidental local working-tree state to define production. Decide whether your production environment follows a protected branch, a tag, or an explicitly selected commit, and make that choice part of the deployment command or release procedure. A deployment should be traceable to one Git revision before it begins.
Free tools Windows power users keep installed
One-click scans. No signup required.
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
Run the first deployment
From the directory containing shipitfile.js, invoke the production environment and the deploy task:
npx shipit production deployThe standard workflow creates a workspace, fetches and checks out the selected revision, creates a release directory below the deployment root, copies the project into that release, updates the current symlink, removes releases beyond keepReleases, and emits lifecycle events. A successful file deployment is not the same as a healthy application: your process reload and HTTP check must still run.
What to verify on the first run
- SSH authentication succeeds without an interactive password prompt.
- The deploy account can create the deployment root and release directories.
- The remote host can read the repository, or the chosen transfer method can access it.
- The new release contains the expected revision and required package files.
- The
currentsymlink points to the new release. - Old releases are removed only after the new release is complete.
- Your process supervisor is reloaded and the application answers its health endpoint.
Perform the first production-shaped run against a staging VPS with the same directory permissions, Node.js version, environment variables, and service definition. That exposes SSH, filesystem, and build assumptions without putting the live service at risk.
Add application-specific install, build, migration, and reload tasks
Shipit cannot know whether your project needs a TypeScript build, asset compilation, database migrations, or a particular service command. Add explicit tasks and attach them to the deployment lifecycle provided by shipit-deploy. The important rule is ordering: install dependencies and build in the new release, run migrations according to a reversible plan, reload only after those steps succeed, then verify the service.
Dependency installation
Use the lockfile-driven command appropriate for your package manager. For npm projects, npm ci is the usual reproducible choice. Decide whether development dependencies are required for the build; do not silently omit packages that compilation needs. If you build in the release directory and then prune development packages, make that sequence explicit and test it.
npm ci
npm run buildThese commands are examples of work your Shipit task should execute on the remote release. They are not a replacement for wiring the commands into your task graph.
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)
Build output and shared files
Keep generated output inside the release when it is version-specific. Store mutable data such as uploads, runtime logs, and environment files outside the release and link or mount them through your deployment convention. Otherwise a release cleanup can remove data the application still needs.
Database migrations
Run migrations as a deliberate deployment step, not as an implicit side effect of starting Node. Confirm whether each migration is backward-compatible with the currently running release, define how to reverse or repair it, and stop the deployment when the migration fails. For applications that require an expand-and-contract schema change, deploy compatibility code first and remove old columns only after all instances have moved.
Recommended Free Tools
Reloading the process supervisor
Shipit does not supervise Node processes. Your task must call the service manager you selected, using a least-privilege command permitted for the deploy account. A reload should target the new current path and preserve availability where your supervisor supports graceful replacement. If your environment uses PM2, its documented SSH deployment interface is separate from Shipit and uses the form pm2 deploy <configuration_file> <environment> <command>; do not assume installing PM2 is part of Shipit.
Health verification
After reload, request an endpoint that proves the new process is serving traffic and can reach essential dependencies. Check the HTTP status, a bounded response time, and an application-level indicator such as the reported revision. A failed health check must fail the deployment and trigger your documented recovery path rather than silently leaving a broken release as current.
How releases, symlinks, and retention work
Shipit’s release-directory model separates immutable release contents from the stable path used by the service. Each deployment creates another release, while current is switched to the selected release after the copy completes. Your process supervisor should run the application from that stable symlink or resolve it consistently through the service definition.
Retention is controlled by keepReleases. A value of five means Shipit keeps the configured number of prior releases according to its cleanup behavior; it does not create a backup of databases, uploaded files, or external services. Measure the disk usage of a real release, account for temporary build space, and choose retention accordingly. If the disk fills during a release, cleanup and deployment can fail together, so monitor free space before increasing the value.
Rank #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
Rollback safely when a release fails
Shipit rollback republishes a previous release through the same symlink mechanism:
npx shipit production rollbackThe rollback flow selects the prior release, points current at it, performs cleanup according to retention settings, and emits rollback events. The deleteOnRollback option controls whether the release being rolled back is deleted. Decide this behavior before an incident; keeping the failed release can aid diagnosis, while deleting it can conserve disk space.
Rollback prerequisites
- Keep more than one known-good release available.
- Ensure the older application can run against the current database schema.
- Keep shared configuration and user data compatible with both releases.
- Know how to reload the process supervisor after the symlink changes.
- Define whether migrations are reversible or require a forward fix.
Test rollback in staging before production. Deploy a deliberately identifiable version, verify that a second release becomes current, run the rollback command, reload the service, and confirm the health endpoint and key user flow. A rollback that only changes files but leaves the process running the old path has not been tested end to end.
Security and reliability checklist
- Account: use a dedicated non-root deploy user and limit its ability to reload only the intended service.
- SSH: use a key with the narrowest practical permissions, protect the private key, and remove access when a person or system no longer needs it.
- Source: pin a branch, tag, or commit intentionally and record the revision in deployment logs.
- Dependencies: install from a committed lockfile and fail on install or build errors.
- Secrets: keep credentials outside Git and ensure they are available to the new release before reload.
- Migrations: use an explicit, tested plan with a recovery procedure.
- Process: reload only after the release is complete, then run an HTTP health check.
- Retention: retain enough releases for incident response while checking available disk space.
- Rollback: rehearse the command and verify application behavior, not just the symlink.
- Observability: collect deployment output, service logs, health-check results, and the deployed revision.
Shipit compared with a process manager or another deployment system
Choose tools by responsibility rather than by brand name. Shipit is strongest when you want JavaScript-defined tasks, SSH-based orchestration, Git-driven releases, symlink switching, retention, and rollback. A process manager is responsible for keeping Node alive, restarting it after failure, and handling service-level reloads. A CI/CD platform may add approvals, artifact storage, secret injection, and audit history.
| Capability | ShipitJS deployment role | What you still need to decide |
|---|---|---|
| SSH and credentials | Connects to configured servers using the selected account and key. | Key rotation, host verification, network restrictions, and least privilege. |
| Release strategy | Creates release directories and switches a current symlink. |
Shared files, disk monitoring, and service path configuration. |
| Source transfer | Uses the configured Git repository and documented checkout behavior. | Revision policy, private dependency access, and reproducible builds. |
| Hooks and tasks | Runs JavaScript tasks and lifecycle events. | Install, build, migration, reload, and health-check commands for your app. |
| Process supervision | Not provided by Shipit. | systemd or another supervisor, restart policy, logs, and graceful reload behavior. |
| Retention and rollback | Keeps configured releases and republishes an earlier release. | Database compatibility, shared data safety, and rollback testing. |
| CI integration | Can be invoked from a pipeline with npx shipit production deploy. |
Approvals, secret storage, concurrency controls, and audit records. |
Troubleshoot common deployment failures
SSH authentication or permission denied
Confirm the key path is correct on the machine running Shipit, the public key is authorized for the specified account, and the account can write to deployTo. If the server uses a non-default port or host-specific SSH option, switch from the shorthand server string to a structured configuration. Do not solve a permission error by granting the deploy user unrestricted root access.
Repository cannot be fetched
Check whether the configured URL is HTTPS or git+ssh, then verify credentials from the context that performs the fetch. A key that can log into the VPS may not be authorized to read a private repository. Pin the intended branch or revision and inspect the deployment output to confirm what was checked out.
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.
Build succeeds locally but fails remotely
Compare Node.js and npm versions, operating-system libraries, environment variables, and lockfiles. Ensure the task runs from the new release directory and that build-time secrets are available without being committed. Make the build fail loudly; proceeding to a reload after a partial build produces an apparently successful but unusable release.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The service still runs the previous code
Check where the process supervisor obtains its working directory and entrypoint. It should resolve the newly switched current release, or your reload task must update the path explicitly. Confirm that the reload actually occurred and inspect the running process revision through the health endpoint.
Rollback changes the symlink but the app remains broken
Verify that the older release is still present, reload the process after rollback, and check compatibility with the current database and shared files. If the failed release was deleted according to deleteOnRollback, use logs and your source repository to diagnose it; do not assume rollback restores external state.
Disk space runs out
Measure release sizes, dependency caches, logs, and temporary build files. Reduce keepReleases only after confirming that your incident-response policy still has enough rollback depth, and clean unrelated disk consumers through a separate maintenance procedure.
A repeatable production runbook
- Review the commit, migration plan, dependency lockfile, and expected health-check result.
- Confirm SSH access, VPS disk space, repository access, and required secrets.
- Run
npx shipit production deployfrom the deployment project. - Watch the install and build tasks; stop on any non-zero exit status.
- Run migrations according to the approved compatibility plan.
- Switch or confirm the
currentsymlink and reload the process supervisor. - Perform the HTTP health check and inspect service logs.
- Record the deployed revision and release path.
- If health checks fail, stop further traffic changes and run the tested rollback procedure.
With this separation of concerns, Shipit provides predictable release mechanics while your application tasks define what “ready for production” means. The result is an SSH-based Node.js deployment that can be repeated, audited, and reversed without treating a process restart as the entire deployment strategy.
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.
