Ready in ten steps.

1. 01

   Get the code

   Either the installation package klxm-studio-<version>.zip from GitHub Releases (with vendor/ and checksum) – or clone the source and install the PHP dependencies.

   git clone https://github.com/KLXM-Opensource/studio.git
   cd studio
   composer install --no-dev

2. 02

   Upload

   Copy the folder contents to httpdocs/ – without tools/node_modules, config/config.local.php, config/sites/ and the contents of storage/, public/media, public/sites, public/pools.

3. 03

   Document root on public

   The domain points to httpdocs/public – code, database and keys stay outside the web root. PHP 8.4 or newer as FPM, display_errors off.

4. 04

   Clean URLs

   Apache: these lines under “Additional Apache directives” (HTTP and HTTPS). nginx only: “location / { try_files $uri $uri/ /index.php$is_args$args; }” – the full nginx template is in the developer handbook.

   FallbackResource /index.php
   # pass the Authorization header for API and MCP
   SetEnvIf Authorization "(.+)" HTTP_AUTHORIZATION=$1

5. 05

   HTTPS and write permissions

   Enable the certificate with a 301 redirect. PHP may write to config/ (on first start), storage/, public/media, public/sites, public/pools, public/assets/ext and public/assets/fonts/installed.

6. 06

   First request and first account

   The first request creates the database and config/config.local.php (with a random app_key and setup token); until the setup is done visitors see “A new website is coming soon”. Then open the setup – or create the account directly.

   php bin/console setup:token        # token and setup address
   php bin/console user:create name@example.org admin

7. 07

   Choose kit and starter content

   After the first sign-in the welcome screen appears: choose a kitkit×In KLXM Studio, the package of design and building blocks for a website: layout, colours, fonts and the matching blocks. A kit can be adapted or switched – the content stays. and decide whether starter content (sample pages, example texts) is installed – or without: empty home page, legal notice and privacy policy as templates. You can also set it in advance:

   <?php // config/sites/default.php
   return ['hosts' => ['www.example.org'], 'theme' => 'basis', 'seed' => 'empty'];   // seed: full | empty | ask

8. 08

   Set up

   Encryption (key pair for requests – the secret key is shown only once), e-mail sending with a test mail, canonical address; then the kit’s central details. The overview shows a checklist.

9. 09

   Scheduled tasks

   Everything runs without croncron×Scheduling service of the server that starts tasks regularly on its own – for example updating the search index, creating backups or fetching feeds.en.wikipedia.org ↗ (opens in a new tab), but some things only on the side. Recommended:

   */15 * * * *  cd /path && php bin/console search:index --all
   30 3 * * *    cd /path && php bin/console search:index --all --full
   15 4 * * *    cd /path && php bin/console inbox:purge --all
   */5 * * * *   cd /path && php bin/console ai:jobs --all
   0 2 * * *     cd /path && php bin/console site:backup --all --keep=14

10. 10

    Check

    All green? Then the installation is done. /health returns the same state without secrets for your monitoring.

    php bin/console health

In detail with the nginx template, a custom admin address and special cases: developer handbook → Installation.