Deploy WordPress on a Cloud Workspace

WordPress on FlyNode runs as an app on your Cloud Workspace. There are no separate WordPress plans: the site uses the memory, CPU, storage and app count of the workspace it runs on. The sizes are on the Cloud page.

Choose the right template

Open Templates in your dashboard and pick WordPress (OpenLiteSpeed + Redis). It runs on the OpenLiteSpeed web server with a MariaDB database and Redis, and it is the template that has the Staging, Security and Resource Usage features described in this section.

Deploy it

1. Open Templates and choose WordPress (OpenLiteSpeed + Redis).
2. Pick the workspace to run it on, if you have more than one, and start the deploy.
3. Wait until the app shows Running. The first start takes a few minutes.
4. Open the site address on the app's Overview tab (it ends in .flynode.io). WordPress shows its installer.
5. Enter a site title, an administrator name, a strong password and your email. Do not call the administrator admin: it is the first name attackers try.

After the installer, use 1-Click WP-Admin on the app page. It signs you in without a password; the link works once and expires after 5 minutes.

What the tabs do

• Overview: the live address and live CPU, memory and storage use. The Resource usage link opens the history (see Resource Usage and Choosing a Plan).
• Staging: a safe copy to test on, and Push to Production (see Staging and Push to Production).
• File Manager: upload and edit files in your browser (see WordPress Login, File Manager and Database Tools).
• Security: updates, file checks, sign-in protection, firewall and the activity log.
• Settings: the one-click login and the app's other settings.
• Backup, Custom Domain and Database.

Your own domain

The site starts on a free .flynode.io address. To use your own domain, follow Custom Domains for Your Apps.

Resources

FlyNode sizes the database and cache memory to your workspace automatically. If the site needs more room, change the workspace size; the Resource Usage page tells you when that is worth doing.

Next: create a staging copy before you change anything on the live site, and review the Security tab.