Getting started with Webcore WordPress
Webcore manages WordPress sites across one or more hosting nodes from a central Panel. Each managed production site has its own system user, document root, MariaDB database, PHP runtime and web-server configuration.
Create or import
Use Create Site for a new WordPress installation. Use Import Site when an existing WordPress site or supported backup package needs to be brought under Webcore management.
When no destination node is explicitly selected, the platform can use capacity-aware placement to choose a suitable active hosting node. Platform administrators can also select infrastructure deliberately when the workload has a specific placement requirement.
Site management
After creation or import, site management is divided into focused areas including WordPress, Preview & Staging, Hosting Settings, Backups, DNS, SSL and Logs. Additional site tools include Git deployment, File Manager, performance/cache controls, malware scanning, scheduled tasks and diagnostics where available to the user's role.
The site status control provides lifecycle actions such as enabling/disabling a site and, for authorised administrators, moving it between hosting nodes.
Before DNS cutover
If the production hostname still points to another provider, use Preview to inspect the exact managed production installation through a temporary Webcore hostname. Preview does not clone the WordPress database.
For changes that require an independent writable copy, use Staging instead. Staging has its own files and database and can later be pushed to production with a production safety snapshot created first.
Safe operating pattern
- Keep production backups enabled and verify that usable recovery points exist.
- Use Preview for non-destructive pre-cutover inspection.
- Use Staging for application changes, testing and backup validation.
- Use Git deployment for code that is maintained in a repository rather than copying it manually.
- Create or retain a recovery point before destructive operations.
- Validate DNS, SSL, caches and important application functions after cutover or infrastructure changes.
Preview and Staging solve different problems. Preview exposes the existing managed site through another hostname; Staging creates an independent WordPress copy.