Skip to main content

ClassicPress

ClassicPress is a community-led content management system with a traditional editor and a familiar WordPress-style administration experience. It is suited to business websites, publishing, and teams that prefer the classic editing workflow.

Before You Deploy​

You need permission to create services, an administrator email, and an initial administrator password. ClassicPress accounts are separate from your Moltern account.

ClassicPress requires MariaDB. Choose a new database for an isolated website, or select a compatible existing dependency when the deploy form offers one. Review that choice before confirming because the selected database becomes part of the site's data boundary.

Deploy ClassicPress​

  1. Open Services, search for ClassicPress, and select Deploy.
  2. Name the service and choose its environment.
  3. Enter the initial administrator email and password.
  4. Review the MariaDB dependency and Capacity and scaling settings.
  5. Select Preview deploy, review the combined impact, then Confirm deploy.
  6. Wait for the site and database to report Running.
  7. Open the generated URL. Moltern completes the initial installation, so the public URL should show a working site rather than the database installer.

ClassicPress capacity and required MariaDB choices in the Moltern deployment form

Create And Publish Content​

  1. Open /wp-login.php on the site URL.
  2. Sign in as admin with the password entered during deployment.
  3. Open Pages > Add New.
  4. Create the page with the classic editor and select Publish.
  5. Open the public page, reload it, and confirm the content is readable.

A designed customer operations brief published on a real ClassicPress service running on Moltern

Use Appearance to select a theme and Plugins to extend the site. Treat plugins and themes as application code: verify the source, updates, and required permissions before enabling them.

Credentials And Integrations​

The initial ClassicPress login is created from the deploy form. If the password is changed inside ClassicPress, the original deployment value does not automatically become the new application password.

For an external integration, create a dedicated ClassicPress user with the minimum role required. Store any application password or API token in the consumer's protected configuration rather than in source code or agent notes.

Capacity, Persistence, And Cleanup​

ClassicPress files and uploads use the service's stored files; posts, settings, and user data are held by MariaDB. Review both workloads when checking storage or changing capacity.

After a stop/start or capacity change, verify the administrator login and one published page. Stopping a service is not a backup. Export important content and database data before deleting the site. Follow the deletion confirmation carefully when deciding whether to remove or retain stored files.

Troubleshooting​

SymptomWhat to check
Database connection errorConfirm the MariaDB dependency is running and inspect the live logs for both workloads.
Administrator login failsUse username admin and the deployment password, unless it was changed later inside ClassicPress.
A page returns 404Re-save the permalink settings and check whether a plugin changed routing behavior.
Theme or plugin causes an errorDisable the latest extension and inspect logs before increasing capacity.
Changes disappear after maintenanceConfirm the service uses stored files and check storage status in Billing.