Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Geckada

开发者 mozzzy
geckada
更新时间 2026年10月15日 20:06
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

backup monitoring google drive health check wordpress maintenance

下载

3.2.231 3.2.160 3.2.246 3.1.5 3.2.144 3.2.119 3.2.149 3.1.1 3.1.3 3.1.2 3.1.4 3.2.0 3.2.20 3.2.19 3.1.149 3.1.6 3.2.161 3.2.163

详情介绍:

Geckada brings monitoring, backups and maintenance into one WordPress plugin. Local backup and restore work without a Geckada account. To use hosted monitoring or remote management, open Geckada > Overview, select Connect to Geckada and approve the site. The plugin contacts Geckada only after you connect it or save a connector token. See External services and Privacy below for details.

安装:

  1. Install and activate Geckada.
  2. Open Geckada > Overview.
  3. Select Connect to Geckada.
  4. Sign in to Geckada and choose or create a project.
  5. Confirm the connection test in WordPress.
Administrators can alternatively paste a connector token from Geckada. Monitoring can be paused and local credentials can be removed from the settings page. Verified local backups can be restored from Geckada > Backups. Manual guided restore requires explicit administrator confirmation, creates a fresh safety backup first, preserves wp-config.php and the active Geckada recovery component, restores in background batches, and finishes with database and filesystem checks. Website activation Connecting to Geckada activates this website against its project using a private connection token. Each project can activate one WordPress website. Your account's project allowance controls new activations. Existing connections remain active when a plan limit is lowered. Remove a connection in Geckada to revoke its token; disconnecting in WordPress removes the local credentials. Local backup and restore features remain available without a Geckada activation. Activation status and plan allowances refresh with successful monitoring heartbeats. Existing clients remain compatible; upgrading adds website-URL checks to monitoring requests.

常见问题:

When does the plugin start contacting Geckada?

Only after a WordPress administrator approves the connection or saves a connector token. Deactivating the plugin stops its scheduled events. The connection can also be paused or disconnected from Geckada > Overview.

What can Geckada remotely control?

When an administrator enables managed backups, Geckada can supply the schedule, retention and backup preset and request a new backup through the authenticated heartbeat. WordPress performs every backup locally and uploads directly to the configured destination. Maintenance Autopilot also lets an authorized Geckada user approve specific plugin, theme, and WordPress core update versions. Geckada sends these limited maintenance commands through heartbeat responses. WordPress checks that the requested versions are still available and creates and verifies a full safety backup before applying updates; connected remote backup uploads must also succeed. If post-update verification fails, Geckada can request an automatic rollback using the verified pre-update archive. WordPress validates that archive against its protected-update history and creates a failed-state safety backup before restoring it. Automatic rollback does not require a separate confirmation in WordPress. Manual guided restores still require explicit confirmation from a logged-in WordPress administrator. These commands are limited to the plugin's backup, update, and rollback workflows; they do not provide a general-purpose remote shell or arbitrary file editor. Recovery keys and object-storage credentials remain in WordPress. Easy Google Drive connection keeps the Google refresh token encrypted on Geckada; WordPress requests short-lived access for direct uploads. Advanced Google setup keeps its credentials in WordPress. Recovery keys and archives are not sent to Geckada. Any archive decryption required for restoration happens locally.

What happens if I lose an encrypted backup recovery key?

Geckada cannot decrypt the archive and does not receive a copy of the key. Download and securely retain every recovery-key file, including older keys kept after a rotation. Importing the matching key makes its encrypted archives restorable. Restore & Migrate works without a Geckada activation. Choose Google Drive, Backblaze B2, Amazon S3 or Upload files. Google Drive uses Geckada's managed sign-in with read-only recovery access; no OAuth client ID or secret is needed. Recovery grants expire after 24 hours and are stored separately from future backup destinations. The Google account must have access to the source files. Managed recovery requires the corresponding Geckada service update. It does not require a site token, create an activation, or use another site's activation. After replacement consent, the plugin checks every part, staged PHP syntax, declared PHP/WordPress requirements and essential database tables. It creates a verified full local safety backup; unavailable remote destinations do not block that local recovery snapshot. The temporary recovery guard isolates backup/restore workers from restored plugins and themes. Public requests stay blocked on failure. Monitoring stays paused until database, filesystem, frontend, login and REST checks pass. Only then can an existing destination activation, or a same-site backup token, be validated through Geckada's existing licensing endpoint. This reuses an existing activation; it does not allocate another site. Different-site backup credentials are never reused. An unavailable/revoked connection does not invalidate a successful restoration: reconnect through Overview using the existing project after success. Previously paused monitoring remains paused. Restored users determine Geckada access. The progress capability remains available if restoration replaces the logged-in administrator. Sign in with restored credentials after completion. If WordPress cannot boot at all, use host-level recovery or prepare a fresh WordPress installation at the intended URL, install Geckada and import the backup there. Preserve the original files/database and backup set first. This plugin is not a bare-metal installer and restoration does not delete unrelated files absent from the backup.

更新日志:

3.2.231 3.2.230 3.2.225 3.2.220 3.2.219 3.2.218 3.2.217 3.2.215 3.2.213 3.2.212 3.2.211 3.2.208 3.2.207 3.2.206 3.2.205 3.2.204 3.2.203 3.2.201 3.2.200 3.2.199 3.2.198 3.2.197 3.2.196 3.2.195 3.2.194 3.2.193 3.2.192 3.2.191 3.2.190 3.2.189 3.2.188 3.2.187 3.2.186 3.2.185 3.2.184 3.2.183 3.2.182 3.2.181 3.2.180 3.2.179 3.2.178 3.2.177 3.2.176 3.2.175 3.2.174 3.2.173 3.2.172 3.2.171 3.2.169 3.2.168 3.2.167 3.2.166 3.2.165 3.2.164 3.2.163 3.2.162 3.2.161 3.2.160 3.2.159 3.2.158 3.2.157 3.2.156 3.2.155 3.2.154 3.2.153 3.2.152 3.2.151 3.2.150 3.2.149 3.2.148 3.2.147 3.2.146 3.2.145 3.2.144 3.2.143 3.2.142 3.2.141 3.2.140 3.2.139 3.2.138 3.2.137 3.2.136 3.2.135 3.2.134 3.2.132 3.2.131 3.2.130 3.2.129 3.2.128 3.2.127 3.2.126 3.2.125 3.2.119 3.2.94 3.2.93 3.2.92 3.2.91 3.2.90 3.2.89 3.2.88 3.2.87 3.2.86 3.2.85 3.2.84 3.2.83 3.2.82 3.2.80 3.2.79 3.2.78 3.2.77 3.2.76 3.2.75 3.2.74 3.2.73 3.2.72 3.2.71 3.2.70 3.2.69 3.2.68 3.2.67 3.2.66 3.2.65 3.2.64 3.2.63 3.2.62 3.2.61 3.2.60 3.2.59 3.2.58 3.2.57 3.2.56 3.2.55 3.2.54 3.2.53 3.2.52 3.2.51 3.2.50 3.2.49 3.2.48 3.2.47 3.2.46 3.2.45 3.2.44 3.2.43 3.2.42 3.2.41 3.2.40 3.2.39 3.2.38 3.2.37 3.2.36 3.2.35 3.2.34 3.2.33 3.2.32 3.2.31 3.2.30 3.2.29 3.2.28 3.2.27 3.2.26 3.2.25 3.2.24 3.2.23 3.2.21 3.2.20 3.2.19 3.2.18 3.2.17 3.2.16 3.2.15 3.2.14 3.2.13 3.2.12 3.2.11 3.2.10 3.2.9 3.2.8 3.2.7 3.2.6 3.2.5 3.2.4 3.2.3 3.2.2 3.2.1 3.2.0 3.1.149 3.1.131 3.1.130 3.1.129 3.1.128 3.1.126 3.1.125 3.1.124 3.1.123 3.1.122 3.1.8 3.1.7 3.1.6 3.1.5 3.1.4 3.1.3 3.1.2 3.1.1 3.1.0 3.0.0 2.9.3 2.9.2 2.9.1 2.9.0 2.8.1 2.8.0 2.7.0 2.6.0 2.5.0 2.4.0 2.3.0 2.2.0 2.1.2 2.1.1 2.1.0 2.0.0