Skip to content

Adding Your First Site

A "site" in Patcherly represents one of your websites or applications that you want to monitor and fix errors for.

What is a Site?

A site is:

  • An application instance (e.g., your production website, staging server, or local development environment)
  • Identified by a URL (e.g., https://myapp.com or http://localhost:3000)
  • Connected via a connector (Python, Node.js, PHP, or WordPress plugin)
  • Monitored for errors automatically

Creating a Site

Step 1: Access Sites Page

  1. Log in to your Patcherly dashboard
  2. Navigate to Sites in the sidebar
  3. Click the "Add Site" button

Step 2: Fill in Site Details

Provide the following information:

  • Name: A friendly name for your site or app (e.g., "Production Website")
  • Type: Connector type (WordPress, PHP, Node, Python, or Other)
  • URL: The base URL of your application (e.g., https://myapp.com). After you save the site, open Edit and use Discover next to the URL to suggest the connector type from the live site.
  • Exclusion paths (optional): Paths to exclude from monitoring
  • Language / Framework (optional): App language (e.g. Python, JavaScript, PHP) and framework (e.g. Django, Express, WordPress). Used as the default for AI prompt template selection; the connector can confirm or override when it reports context.
  • Dry-run (default off for new websites/apps): when on, the connector previews what an approved fix would do (parses the patch, runs safety checks, reports back) but does not change files or restart your application. Turn it on for a staging or sensitive site when you want a safe test, then turn it off so Approve applies for real. Dry-run is also one of the three gates that controls auto-apply - while it's on, auto-apply will not write any files. See Rollback → Dry-run mode.

Step 3: Pair Your Connector

After creating the site or app, click Connect next to it. The connector authenticates via OAuth 2.0 Device Authorization Grant - no key to copy. The installer launches the pairing flow automatically when it finishes; you'll see:

  1. Install the connector on the site server using the one-line command shown for your platform.
  2. The installer finishes and launches pairing automatically. The CLI prints a verification_uri and a short user_code.
  3. Open the printed URL in any browser, sign in, select the website/app, and confirm the user code.
  4. The connector saves credentials to ~/.patcherly/credentials.json (or /root/.patcherly/ when paired with sudo) and starts monitoring.

Need to skip auto-pairing (image baking, CI, batch installs)? Set SKIP_LOGIN=1 before running the installer, then run the pairing command manually later - sudo /opt/patcherly-connector/start.sh login on Linux/macOS, & "$env:USERPROFILE\patcherly-connector\start.ps1" login on Windows, or patcherly login for package installs. See Installing a Connector → Pair manually (or re-pair).

For WordPress: install the Patcherly Connector plugin, then open Patcherly → Home and click Connect with Patcherly.

See Installing a Connector for full details.

Step 4: Verify the connection

After pairing, check Sites in the dashboard - the connector status should update to Connected. If you need connector-specific setup details, see:

Site Limits

Your plan determines how many sites you can have. Visit the Pricing page for current limits. If you need more, consider upgrading your plan.

Managing Sites

After creating a site or app, you can:

  • View site status: See if the connector is connected
  • View errors: See all errors detected for this website/app
  • Re-pair connector: From the site server's INSTALL_DIR, run start.sh login (Linux/macOS) or start.ps1 login (Windows) - or patcherly login for package installs - to issue a fresh OAuth token
  • Enable/Disable: Temporarily disable monitoring
  • Toggle Auto-Analysis: turn on automatic AI analysis for this website/app (requires a plan that includes auto-analysis - see Pricing). When it's on, new errors skip the manual Analyze with AI click. See Auto-Analysis.
  • Delete: Remove a site or app (this also immediately revokes its connector OAuth token - the connector will stop receiving fixes and refresh attempts will return invalid_grant. Re-pair with patcherly login if you restore the website/app.)

Next Steps