Installing FlatPress and checking the first setup

A flat-file application still needs careful file permissions and backups. Confirm the selected release supports the account's PHP version and that its content directories can be written by the correct account user.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find FlatPress and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review the backup destination, update choices and documented writable directories. FlatPress content is stored in files, so do not substitute a database-only recovery plan.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Set the site URL, title and administrator credentials, then create a test post and upload. Plan an off-account backup of the complete content and configuration tree rather than relying on a database-only backup.

Create a harmless test post containing one uploaded image, then take the planned backup of the application's content and configuration files. A database-only backup cannot represent this flat-file publishing workflow.

1. Inspect the archive in a private location and verify that the actual content files, uploaded image and required configuration are present.
2. Restore a copy to an isolated test destination using the application's supported procedure.
3. Open the test post and image and verify the administrator can access that test installation.
4. Check permissions on the restored writable directories without making the entire website world-writable.

Keep the backup away from the public document root and protect its account details. Record the successful test date before making a major theme, plugin or runtime change to the live blog.

Check the post, category or archive view and uploaded image. Create a backup and inspect it to confirm the actual content files are included.

Permission errors should be fixed by checking ownership and the project's documented writable paths. Do not recursively make the whole site world-writable.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Migrating an older blog to WordPress or a current publishing platform
• Creating Web Hosting backups and planning a restore
• Changing PHP versions, extensions and application limits
• Installing b2evolution and checking the first setup

• Softaculous installation workflow
• Softaculous blogs catalogue