iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
To self-host Cachet reliably, deploy the 3.x application on a supported 64-bit Linux VPS, put it behind HTTPS on a dedicated status subdomain, and give its database and uploaded assets persistent storage. The official project currently requires PHP 8.3 or later, Composer, and MariaDB, MySQL, PostgreSQL, or SQLite. You can run those dependencies directly on Linux or use the official Docker Compose workflow. Docker is usually quicker to reproduce; a manual installation fits teams that already operate PHP services. Either way, availability during an incident depends more on isolation, backups, monitoring, and a tested recovery plan than on the installation method.
What Cachet does and what this deployment must provide
Cachet is an open-source, self-hosted status-page application. It presents the state of the services you choose to publish, lets operators post incident updates, and can publish scheduled maintenance. The application is a web service backed by a database, with a public hostname in front of it. Your VPS therefore needs to provide four things:
- An application runtime: Cachet 3.x requires PHP 8.3 or newer and Composer.
- Persistent data: use MariaDB, MySQL, PostgreSQL, or SQLite, plus durable storage for any uploaded assets.
- A public endpoint: point a dedicated status subdomain at the VPS and terminate TLS before traffic reaches Cachet.
- Independent operations: keep the page, its database, and its monitoring path separate from the systems whose health it reports whenever your outage requirements demand that.
A status page hosted on the same network, account, or control plane as your production application can disappear with that application. Independence is not a guarantee—your DNS provider, VPS host, and certificate path can still fail—but separating the page removes a major shared failure domain.
Choose Docker or a manual Linux installation
Both approaches run the same Cachet application. The difference is where the runtime and operational boundaries live.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
| Decision area | Docker/Compose | Manual installation |
|---|---|---|
| Dependency isolation | Packages the application runtime and its dependencies in containers; the host mainly supplies Docker and storage. | Uses the host’s PHP 8.3+ installation, Composer, web server, and database packages. |
| Reproducibility | Compose files and an image or build context can be recorded and recreated on another VPS. | Reproduction depends on documented operating-system packages, PHP modules, Composer state, and web-server configuration. |
| Upgrade control | Pin a stable Cachet release and image/build inputs; run migrations deliberately. | Pin the source release and dependency versions; run the documented upgrade and migration procedure. |
| Operational visibility | Inspect container status and container logs, as well as the reverse proxy and host. | Inspect host service logs, PHP/application logs, the web server, and the database directly. |
| Recovery | Back up database data, uploaded assets, environment values, and named volumes or bind-mount locations. | Back up the database, uploaded assets, application configuration, and the source/dependency state needed to rebuild. |
| Best fit | A team that wants a repeatable deployment and already operates Compose. | A team that standardizes PHP applications directly on Linux and has host-level service automation. |
Do not treat Docker as a backup strategy. A new container is disposable; the database and persistent files are not. Conversely, a manual install is not automatically more reliable simply because it has fewer containers. Pick the path your team can patch, observe, restore, and hand over at 03:00.
Prepare the Linux VPS before installing Cachet
Use a supported, restricted host
- Choose a supported 64-bit Linux distribution and apply current security updates.
- Create a non-root administrative account. Use SSH keys rather than password authentication, and restrict SSH by source address when practical.
- Enable the host firewall with only the required public services: HTTP and HTTPS. Keep SSH restricted to your administration sources.
- Install or enable automatic security updates, and decide who receives alerts when an update requires a reboot.
Cachet’s application port should not be your public listener. Bind it to the host or an internal container network and let a reverse proxy accept internet traffic. This gives you one place to enforce TLS, redirects, request limits, and access logging.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Set DNS and the public hostname
- Choose a dedicated name such as
status.example.comrather than placing the page under the primary application domain. - Create an A or AAAA record for the VPS address. If you use an edge proxy, follow that provider’s origin and certificate requirements and retain a direct recovery path.
- Wait for the record to resolve from outside your network before requesting a certificate.
- Plan an alternate communication channel and, if possible, a pre-written maintenance page for a DNS, VPS, or email-provider outage.
Protect data and secrets from the start
Use persistent storage for the database. In Compose, choose named volumes or explicit bind mounts and record their locations. In a manual installation, place the database on a persistent filesystem and identify the directory containing uploaded assets. Store the environment file and the Cachet APP_KEY with restrictive permissions; never commit either to a public repository. The application key is a secret, not a cosmetic setting: treat it like a credential and rotate related access when staff or systems change.
Deploy Cachet with the official Docker Compose workflow
The project’s Docker documentation uses a repository clone, environment configuration, a stable release selection, a build/start cycle, and an application-key generation step. The exact repository layout can change, so keep the checked-out release and Compose file under version control or in an administrative archive.
1. Obtain and pin the project
- Install Docker Engine and the Compose plugin supported by your Linux distribution.
- Clone the official Cachet Docker repository onto the VPS or into your deployment workspace.
- Check out a stable, tagged Cachet release. Do not deploy an unpinned
latestor development build to production; a moving tag can change without the rollback point you expect. - Record the tag, commit or image digest when available, the Compose file, environment values, volume locations, and your rollback procedure.
2. Configure the Compose environment
Edit the environment variables in docker-compose.yml as directed by the release documentation. Set the public URL, database connection values, mail settings if you will use notifications, and persistent volume mappings. Keep credentials out of the Compose file when your deployment system supports a protected environment file or secret store. Check file permissions before starting the stack.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
3. Build and start the stack
From the directory containing the Compose file, run the documented build and startup commands:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesdocker-compose build
docker-compose up
The documented container listens on port 8000 by default. The example Compose configuration exposes that service on host port 80. Treat those values as the release’s documented defaults, not a reason to expose port 8000 directly to the internet. For production, place a reverse proxy on the public interface, forward internally to the Cachet service, and serve the site over HTTPS.
4. Generate and persist the application key
With the containers running, execute the Artisan key-generation command inside the running Cachet container:
php artisan key:generate
Copy the resulting base64: value into the Compose configuration or protected environment file exactly as generated, then restart the stack so every application process uses the same key. Do not generate a different key for each restart, and do not publish the value in a ticket, repository, or shell transcript. If you lose the key, recovery may require restoring the original protected value rather than generating a replacement.
5. Put HTTPS in front of Cachet
Configure Nginx, Caddy, or another reverse proxy to obtain and renew a certificate for the status hostname, redirect HTTP to HTTPS, and proxy requests to the private Cachet listener. Permit the proxy’s public ports through the firewall; leave the application port reachable only from localhost or the internal container network. Verify that the browser sees a valid certificate, that the application generates links with the HTTPS hostname, and that proxy access logs do not disclose environment values.
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 & 11Rank #3
- 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
6. Verify the deployment before announcing it
- Open the public hostname from a network other than the VPS and confirm the page loads over HTTPS.
- Check that the administrator can sign in and that a normal viewer cannot reach administrative paths without authentication.
- Confirm that a restart does not erase components, incidents, or uploaded assets.
- Stop and start the stack once under supervision; record the commands and expected recovery time.
- Capture the running release tag, container names, volume locations, and log locations in your operations documentation.
Install Cachet directly on Linux when PHP is your standard
The manual route follows the project’s PHP application requirements rather than a fixed command list. Cachet 3.x requires PHP 8.3 or later, Composer, and one supported database: MariaDB, MySQL, PostgreSQL, or SQLite. Package names, required PHP extensions, web-server directives, and migration commands can change between 3.x releases, so use the current Cachet installation and upgrade documentation for the release you selected instead of copying an old command sequence.
Manual-install sequence
- Prepare the host: apply the VPS hardening steps above, install PHP 8.3 or newer and the extensions specified by the selected Cachet release, install Composer, and install your chosen database.
- Obtain a stable source release: download or clone the Cachet source and pin the release. Keep the source revision and Composer lock state needed for a rebuild.
- Create the database and account: use a dedicated database and least-privileged credentials. Do not reuse the primary application’s database account.
- Configure the environment: set the public URL, database connection, timezone, mail settings, and a strong unique
APP_KEYaccording to the current documentation. Protect the environment file with restrictive permissions. - Run the documented installer and migrations: execute the release’s current installation commands from the application directory. Do not substitute commands from a different Cachet major version.
- Serve the public directory: configure the web server to expose Cachet’s public directory, not the repository root or environment file. Pass requests through HTTPS at the reverse proxy.
- Test persistence and upgrades: create a component and a test incident, restart the relevant services, and confirm both records remain before inviting subscribers.
Manual installation gives you direct access to host logs and service managers, but it also makes PHP, Composer, web-server, and database compatibility your responsibility. Document the package versions and configuration so another administrator can reproduce the host.
Complete Cachet’s first-run configuration
Create the administrative workflow
After the public page is reachable, create the administrator account and sign in through the secured hostname. Set the public site name and timezone, then define component groups and components that correspond to services readers actually recognize. Avoid exposing internal implementation names that do not help a customer decide whether an incident affects them.
Practice an incident and maintenance notice
Publish a maintenance notice before a real outage so the team exercises the complete workflow. Use realistic component states and write updates with four fields in plain language: the timestamp, customer impact, mitigation or current action, and the time of the next update. Keep the public page concise; a reader should be able to identify the affected service and latest state without interpreting internal logs.
Configure mail only after the page works
Mail delivery is a secondary dependency. First verify the page, authentication, and incident workflow. Then configure the SMTP or mail credentials required by your release, check the sender policy for the domain, and send a test. If subscribers are enabled, test confirmation and unsubscribe behavior from an external mailbox. Store mail credentials separately from public content and rotate them when ownership changes.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Use the API without surrendering incident control
The official API represents schedules and their related components and updates in JSON responses. That makes it suitable for controlled integrations that create incidents, change component status, or publish scheduled maintenance from monitoring and deployment systems.
- Issue a dedicated credential for each integration and protect it like any other secret.
- Rate-limit automation and log the actor, request, result, and incident identifier.
- Require an operator review for high-impact changes or provide an explicit manual override.
- Prevent a failed monitor from replacing a carefully written manual incident with an incorrect “operational” state.
- Test API failures, expired credentials, duplicate events, and network timeouts before enabling automatic publication.
Automation should reduce typing during an incident, not remove judgment. Keep a documented manual procedure for posting an update when the monitoring system or integration is unavailable.
Operate the status page as production infrastructure
Backups and restoration
- Back up the Cachet database on a schedule appropriate to the incident history you must retain.
- Back up uploaded assets and any persistent application files in addition to the database.
- Encrypt backup copies, restrict access, and keep at least one copy outside the VPS.
- Record the exact release, environment values, database type, volume or bind-mount paths, and reverse-proxy configuration needed for a rebuild.
- Restore into a separate environment on a schedule. A backup that has never been restored is only an assumption.
Upgrades and rollback
Pin the Cachet release rather than following a moving latest tag. Before an upgrade, read the project’s release and upgrade notes, snapshot or back up the database and assets, and schedule a maintenance window. Apply migrations using the commands for that release, verify the public page and administrator workflow, and keep the previous release and a tested restore path available. Rollback may require restoring both the application version and the database state; rolling back only the container or source tree can leave incompatible migrations behind.
External monitoring
Monitor HTTPS from outside the VPS and alert on more than a simple HTTP status. Track certificate expiry, DNS resolution, disk usage, database health, container restarts or host service failures, and backup freshness. Monitoring from the same host cannot reliably tell you that the public page is reachable. Keep alerts and credentials independent enough that a production outage does not silence the status-page alert.
Security maintenance
- Patch the operating system, PHP runtime, database, reverse proxy, Docker engine, and Cachet release.
- Restrict administrative access and review authentication and proxy logs for unexpected access.
- Use a strong unique
APP_KEYand protected database and mail credentials. - Rotate credentials when employees, contractors, integrations, or hosting accounts change.
- Keep the application listener private and expose only the reverse proxy’s HTTPS endpoint.
Troubleshoot common deployment failures
The page is reachable locally but not publicly
Check DNS resolution, the VPS firewall, the reverse proxy listener, and the certificate’s hostname. Confirm that the proxy can reach the private Cachet port and that the application is not bound only to an inaccessible interface. Test from an external network rather than relying on a browser inside the VPS.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Containers start, but data disappears after a restart
Inspect the Compose volume or bind-mount declarations and verify that the database and uploaded assets are written to persistent storage. A container filesystem is not a durable database. Confirm persistence by creating a test component, restarting the stack, and checking the record afterward.
Free tools Windows power users keep installed
One-click scans. No signup required.
The application reports a key or environment error
Verify that the generated base64: application key was copied without truncation, is available to every application process, and is loaded from the environment file or Compose configuration actually used at startup. Restart after correcting the value and keep the secret out of logs and source control.
Mail or subscriber confirmation fails
Recheck credentials, sender-domain policy, outbound firewall rules, and the mail provider’s logs. Send a controlled test, then verify both confirmation and unsubscribe links from outside the VPS. Do not treat a functioning web page as proof that mail delivery works.
An automated update overwrites a human incident
Disable or pause the integration, restore the intended component state manually, and inspect the integration’s retry and authorization behavior. Add an operator approval gate or conflict rule so monitoring cannot silently replace a manually posted incident.
Pre-launch checklist
- Stable Cachet release selected and recorded.
- PHP 8.3+, Composer, and a supported database available for the chosen installation path.
- Dedicated status DNS name resolves to the intended endpoint.
- HTTPS certificate is valid and renews automatically or has an owner and reminder.
- Cachet’s application port is private; only SSH, HTTP, and HTTPS are exposed as required.
- Database and uploaded assets persist across restarts.
- Administrator account, components, timezone, and public site name configured.
- Test maintenance notice, incident update, mail delivery, subscriber confirmation, and unsubscribe flow completed.
- Encrypted backups exist and a separate-environment restore has succeeded.
- External HTTPS, disk, database, restart, certificate, and backup-freshness monitoring is alerting correctly.
- Upgrade, rollback, and alternate-communication procedures are written where the on-call team can reach them.
The Bottom Line
Use the official Docker Compose path when reproducibility and dependency isolation matter most; use a manual installation when your team already operates PHP directly on Linux. Pin the release, keep the listener behind HTTPS, persist and test the database and assets, protect the application key, and monitor the public page from outside the VPS. Those operating practices—not the choice of packaging alone—determine whether Cachet remains available when your other systems are not.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →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.

