Ramza 1.0

1. Requirements

Before installing: create an empty database and database user. Do not import the SQL file manually unless support asks you to.

2. Installation

1. Extract the buyer ZIP. Upload the contents of the Script folder to the domain or subfolder that will run Ramza.
2. Open the site URL. A fresh package redirects to /install.
3. Pass the readiness check. Fix any missing PHP module or write permission before continuing.
4. Enter the empty database. Use the database host, port, name, username and password created for this site.
5. Activate the license. Enter the buyer username and purchase code supplied for this installation.
6. Create the administrator. Use a private email address and a unique password.
7. Review and finish. Sign in, then remove write access from config.php if your host allows it.

3. License activation

One license is assigned to one production domain. The installer sends the purchase code, buyer name and normalized site URL to the Ramza license service. Purchase codes and service secrets are not placed in URLs.

Local development and a public production domain are separate installations. Ask support before moving an active license.

4. First admin setup

Open Admin panel > Settings and complete these items first:

• Set the site name, URL, email sender, timezone and language.
• Configure upload limits and allowed media.
• Choose local or external object storage and run its connection test.
• Configure email delivery and send a test message.
• Review registration, privacy, moderation and user permissions.
• Set the cron job and confirm System Status has no blocking error.

5. Reaction icons

Open Admin panel > Manage Features > Reactions. The same active reaction library is used by posts, reels, comments, messages, notifications and API responses.

Icons must be 16 to 512 pixels, no larger than 1 MB. PNG with a transparent background is recommended. At least one reaction must remain active.

6. Storage and media

Open Admin panel > Settings > Storage & CDN. Ramza supports local storage and configured object-storage providers such as Amazon S3-compatible services and Cloudflare R2.

1. Enter the endpoint, region, bucket, access key, secret and public base URL.
2. Use Test connection before enabling the provider.
3. Upload an image, video and reel. Confirm each public URL loads in a private browser window.
4. Keep local files until the remote upload and cleanup job has completed.

Video: install FFmpeg and set its absolute binary path if thumbnails or conversions are enabled. Object storage also needs correct CORS and content-type rules.

7. AI providers

Open Admin panel > Settings > AI. Select a supported provider or use Custom AI for an OpenAI-compatible endpoint.

• Enter the base URL, API key and model ID exactly as supplied by the provider.
• Use the connection test before enabling user features.
• Set usage limits and permissions.
• Keep API keys in server configuration; never place them in theme JavaScript.

The site assistant and premium AI tools appear only when their add-on entitlement and admin setting are active.

8. Progressive Web App

1. Use HTTPS and confirm the final site URL.
2. Open Admin panel > Apps > PWA.
3. Upload square 192x192 and 512x512 PNG icons.
4. Set the app name, short name, colors and offline page.
5. Enable PWA and the install banner, then test in a private window.

9. Add-ons, calls and live video

The Add-ons Center shows the entitlement and configuration state for the advanced algorithm, site assistant, WebRTC and Cloudflare image tools. Locked add-ons link to Raccodex support.

For calls, open Settings > Video & Audio. Choose WebRTC or the configured fallback provider. Production WebRTC requires HTTPS and a reachable STUN/TURN service. The included TURN files are deployment templates; the server process must run separately and must not expose its long-term secret.

10. Feed algorithm

Open Admin panel > Algorithm. When the paid algorithm add-on is active, ranking can use follows, engagement, watch time, freshness, interests, quality, location and diversity. Reels use the same control layer with reel-specific watch signals.

When disabled, Ramza uses its standard chronological/random feed behavior. Start with conservative weights, review the diagnostics, and change one group of settings at a time.

11. Payments

Configure only the gateways your business uses. Use sandbox credentials first, set the exact callback URLs shown in the admin panel, and verify one successful and one failed payment before production.

12. Cron jobs

Run cron-job.php with the PHP CLI at the interval shown in the admin panel. A common cPanel command is:

/usr/local/bin/php /home/ACCOUNT/public_html/cron-job.php >/dev/null 2>&1

Replace the path with the value from your host. Confirm the last-run time changes in System Status.

13. Updates

Automatic update

1. Back up files and database.
2. Open Admin panel > System > Updates.
3. Check the signed update, review its notes, install it, and run the database step if offered.
4. Clear cache and test sign-in, feed, uploads, admin and cron.

Manual update

Use the update package supplied by Raccodex. Follow its included file list and migration order. Do not replace config.php or the upload directory.

14. Security checklist

• Use HTTPS, a supported PHP version and automatic server security updates.
• Keep config.php, license-server secrets and TURN secrets out of public downloads.
• Use unique admin, database and service passwords.
• Restrict database access to the application host.
• Schedule database and upload backups and test a restore.
• Review System Debugger reports before sending them; redact personal data and secrets.

15. Junior developer map

Work on a copy, use a disposable database, keep changes small, run PHP lint, and test both a normal page load and its AJAX action. Do not edit third-party files under vendor unless upgrading the whole package.

16. Troubleshooting

17. Support

Before contacting support, collect the Ramza version, PHP version, page URL, exact steps, expected result, screenshot, server error excerpt and browser Network response. Remove passwords, purchase codes, API keys and personal data.

Changelog

1.0 - Initial release.