How to Install KAS — Complete Step-by-Step Guide

Install a new KAS website and administration area using an authorized package, independent database, protected configuration, native updates and verified authentication.

KAS is a PHP framework with a website frontend and a native administration area. Installation connects an authorized package to a new database, creates the initial administration structure, applies the required native updates and initializes the project theme. This guide is for a new installation on a server you are authorized to manage.

Do not run fresh installation against an existing customer database. An existing application needs its normal update or a separately planned migration, with a verified backup.

1. Check the prerequisites

You need control of the hostname, hosting/document root, HTTPS and a database account; an authorized KAS package and licence; and access to the approved protected configuration-provisioning process. Keep a secure credential manager available. You also need a browser, a supported background file-transfer tool and access to appropriately restricted PHP/application logs.

The application and its theme must be compatible with the selected package. PHP extensions include mysqli, OpenSSL, cURL and Sodium for encrypted project credentials. Document rendering and theme dependencies can add requirements. Confirm them with the package provider before installing.

2. Obtain the package and licence

Obtain a complete installation package and a licence authorized for the intended hostname through the normal KAS distribution/licensing channel. Confirm package integrity and the intended version with the provider. Do not assume a source-repository archive includes every installation prerequisite, private provisioning item or working project theme.

Never obtain an installation by copying another customer's database, private configuration, account passwords, provider tokens or generated files.

3. Confirm server compatibility

Use the PHP/database combinations supported by your package provider and hosting operator. Core compatibility includes PHP7.4 and MariaDB10.3 code paths, but those old upstream versions are not a recommendation to deploy unmaintained software. Ask the provider to verify the maintained runtime you intend to use, its SQL behavior and required extensions.

Confirm the supported web-server rewrite configuration, PHP execution identity, writable runtime directories, memory/upload limits and error-log location. Do not enable public phpinfo or database tools to perform this check.

4. Choose a new or existing hosting account

A new customer project can use a new hosting account. An existing account can host an additional domain/subdomain with its own document root and database. Check quotas and ownership before proceeding.

Applications in one hosting account can share an operating-system user. Separate folders, databases and .htaccess files do not create filesystem isolation. Confirm that this trust boundary is appropriate, particularly when an installation will have public users or file-upload capabilities.

5. Configure the domain and DNS

For example, a project can use https://demo.example.com/. Create only the approved DNS record pointing to the correct hosting origin and the matching hosting domain/subdomain entry. Check existing A, AAAA and CNAME records first; do not replace unrelated records automatically.

When a DNS proxy is enabled, DNS lookup results may show the proxy's edge addresses. Verify the actual configured origin through the authorized hosting/DNS controls.

6. Verify HTTPS and the document root

The hostname must resolve to the directory containing this installation's index.php, _settings.php, kas/ and rp_framework/. Native forms and redirects use / and /kas, so a directory viewed through another application's URL path is not automatically a supported equivalent.

Verify the certificate, hostname, PHP execution and rewrite behavior. Protect the installer before exposing it. Confirm that PHP configuration, backups, logs, cache and session files cannot be downloaded. If a proxy terminates TLS, use the hosting operator's trusted HTTPS configuration; do not trust arbitrary client-supplied forwarded headers.

7. Create an independent empty database and user

Use the hosting provider's database tools to create and correctly map a new empty database and a dedicated user. Give that user the privileges needed for KAS tables, migrations and views on this database only. Do not grant global privileges or permission to grant access to others.

Example names are account_project for the database and account_app for the user. They do not have to match. Use the exact final names returned by the host: prefix and length rules differ between accounts and database engines.

8. Generate and protect credentials

Generate a strong unique database password through your approved credential manager. Preserve it exactly, including any quotes or backslashes. Enter it only through approved protected channels. Do not put passwords in chat, scripts committed to Git, screenshots, URLs, shell arguments or diagnostic logs.

Keep database credentials separate from administrator passwords, encryption keys and provider credentials. A backup is useful only when its matching recovery material is retained securely and its restoration has been verified.

9. Transfer the installation files

Check that the destination is absent or empty and belongs to this installation task. Stop on existing files, symlinked targets, unexpected ownership or a nonempty destination. Do not synchronize an entire hosting account or delete files to make a package fit.

Use the approved background transfer workflow with a verified server identity and an exact file manifest. Compare uploaded bytes against the expected hashes through independent read-back. Do not upload repository metadata, developer tools, private local configuration or another application's runtime data.

10. Prepare protected configuration prerequisites

Before visiting /kas, have the authorized operator provision the installation's required private SQL/PHP encryption material, administrator initialization credentials, compatible initialization representation, distinct project-vault master key and protected installation token through the approved process.

The established private _secrets.php convention is separate from public package distribution. The setup form does not generate all of these prerequisites. Do not borrow keys from another installation, publish a complete private configuration file, or disable a missing-key check to continue.

11. Open and complete the native setup form

Open the intended HTTPS website root. When _config.php is absent, the native Configuration Setup form appears. Obtain the protected installation token from the authorized operator; it proves permission to begin this new installation. The form also supplies a session-bound CSRF token automatically.

Field What to enter
Protected installation token The privately provisioned token for this installation. Treat it as a secret.
Licence Code The authorized KAS licence supplied for this project.
Business Name The business/project display name.
Primary Domain Domain text without scheme/path, for example example.com.
Database Name The exact database identifier returned by the host.
Database User The exact dedicated username returned by the host.
Database Password The generated password, unchanged.
Host The actual database hostname/address supplied by the host.
Port The actual database port, commonly3306; use the host's value.
Socket The host's socket configuration; the form's null value represents no socket.
Theme Name The chosen lowercase-letter name, for example myproject.
Subdomain Optional hostname prefix, such as demo; leave blank for no additional prefix.
Canonical The full preferred website URL, for example https://demo.example.com.
Use SSL Enable for the production HTTPS site.
Debug Leave off for production. Enable diagnostics only through an authorized protected troubleshooting process.

Review the complete domain/subdomain combination before submission. For the example above, example.com plus demo produces https://demo.example.com. Do not include /kas in the canonical website URL.

Setup validates fields on the server and preserves passwords exactly. If rejected, review the named field or protected authorization prerequisite; the form does not display submitted secrets back to you. Do not retry by removing punctuation from the password or guessing different credentials.

12. Understand the redirect to /kas

A successful form submission saves the installation-owned configuration and sends a303 redirect to /kas. This means configuration was committed; it does not mean every schema update or theme step is finished.

Setup refuses to overwrite an existing configuration. A recovery checkpoint records the owned installation and target connection without exposing credentials in progress messages.

13. Create the base schema and complete native updates

On first administrative access, KAS verifies the protected prerequisites, matching installation ownership and an empty target schema before creating base tables and the native operator accounts. If interrupted during DDL, initialization blocks automatic replay so an operator can inspect and recover safely.

Allow the normal licensed KAS update check to run when its native conditions permit it. Follow its real prompts/status and wait for database and file synchronization to finish. If the interface presents Check for Updates, use the authorized normal action; do not force unpublished content or change a version marker manually.

The package provider must confirm that the installation package and its migration control files support the complete fresh-database path, including any protected inputs required by historical migrations. If a database update fails, retain its checkpoint and sanitized error code for operator review. Do not ignore failed statements, create guessed business tables, drop foreign keys or change deletion rules to get past the error.

The existing LOCAL/localhost mode excludes the ordinary network updater. Local testing must therefore distinguish component/schema tests from a full licensed installation/update rehearsal. Opening /kas, seeing a login page or receiving HTTP200 does not prove the update chain completed.

14. Initialize the frontend and theme

After native updates finish, open the website root. If required updates or file synchronization are still pending, the continuation page links back to administration. Complete that stage before proceeding.

Frontend initialization creates or renames the matching default template directories to the chosen theme name and saves the project/site URL settings. It preserves unrelated themes and stops on target collisions. It does not erase customer records, clear provider settings or reset installed version markers. The old UPDATETHEME flag is not a database-reset permission.

After successful initialization, the active checkpoint clears. Ordinary subsequent visits do not replay new-install DDL. Keep private configuration and recovery material protected.

15. Sign in and configure the project

Use the authorized native administrator identity and its securely retained initialization password. Do not use another installation's credentials or disclose the initial operator account to general reviewers/users.

Through native administration, verify the business identity, website URL, timezone, language, currency, branding and other project settings. Configure additional users with only the privileges they need. External messaging/payment credentials and service activation are separate authorized work; installation does not authorize sending messages or charging accounts.

16. Initialize menu definitions when required

After receiving new section definitions, log out and visit /kas/init. Accept the native initialization confirmation when applicable and wait for it to return to login. Sign in normally and verify the intended menus and privileges.

Menu initialization materializes registered definitions. It is different from database migrations and does not update other installations. An already-authenticated session can redirect before processing the initialization flag, which is why logout matters.

17. Exercise representative native functions

Use disposable synthetic records to verify an allowed page, form save, table listing, client/invoice workflow and original document handler appropriate to the package/theme. Check saved values and totals, not merely a success notification. Verify that a lower-privilege user cannot access protected routes directly.

Test login, logout, session timeout, the frontend and assets, canonical redirects and any deliberately permitted hostname aliases. Keep real customer information and real message destinations out of installation tests.

18. Troubleshoot without destructive retries

  • Setup authorization fails: reload the form, confirm the correct installation token and trusted HTTPS, and have the operator inspect private provisioning. Never publish the token.
  • Configuration already exists: stop fresh setup. Review whether this is an existing installation, a previous attempt or a recovery task. Legacy automatic config conversion has its own trusted path and preserves a checked backup; it is not a public reinstall operation.
  • Backup already exists: retain it and request operator review. Do not overwrite or delete it merely to silence an error.
  • Database creation is interrupted: preserve the configuration/checkpoint and inspect the exact failed stage. DDL is not one rollbackable transaction. Restore verified task-owned resources or prepare a reviewed repair; do not blindly replay all migrations.
  • A native update reports SQL/file errors: stop dependent steps, retain sanitized evidence and ask the package maintainer for the supported correction. Do not skip versions, mark failed migrations complete or edit published migration history casually.
  • Theme target collision: preserve both directories and inspect their ownership/content before choosing a recovery. A flag must never authorize deleting populated data.
  • Frontend says updates are pending: return to administration, finish the normal licensed update workflow and retry the frontend afterward.

Use restricted logs to distinguish configuration, database, licensing, routing and theme errors. Share sanitized codes and source paths; omit credentials, request bodies, query values and secret-bearing stack arguments.

19. Review post-installation security

Keep debug off; verify sensitive-file HTTP denial, configuration permissions, protected backups and unique encryption material. Confirm database-only grants, dedicated user identities, host-only/session separation where supported, HTTPS and safe proxy settings. Ensure uploads cannot execute arbitrary PHP.

Check that private/admin responses are not publicly cached. Robots/noindex is not access control. Remove only task-owned temporary diagnostics through an approved cleanup procedure. Maintain account-revocation and restore procedures, and preserve matching private keys securely with backup recovery planning.

20. Confirm readiness

The installation is ready only after each applicable item is verified:

  • Configuration values and hostname are correct; no secrets are exposed.
  • Base schema and required native migrations/file synchronization completed without unresolved failures.
  • Normal administrator authentication, logout and privilege denial work.
  • Required menu initialization completed while logged out.
  • Frontend/theme directories, canonical URL, language/timezone and assets are correct.
  • Representative saves, totals and document rendering work using synthetic data.
  • Repeated access does not repeat setup or destructive initialization.
  • Logs contain no unresolved installation errors; backups and recovery are verified.

If any item remains unverified, retain its exact blocker and finish that check before handing the installation to normal users. A file upload, version label or successful login-page response alone is not installation acceptance.