Quick Install / Apps

Install WebBlocks CMS or a clean Laravel application skeleton with safe .env handling, APP_KEY protection, cleanup, and retry support.

Quick Install Options

Open Sites → Apps → Quick Install to install supported apps into an existing site. WebBlocks CMS remains available, and Laravel App can create a clean latest Laravel skeleton in the site's web_root project path.

Laravel App

Laravel App installs only the clean Laravel application skeleton. It does not install QuizTem, private packages, GitHub tokens, Node dependencies, Vite builds, or Tailwind compilation.

  • The target web root must be safely empty/installable.
  • The installer runs composer create-project laravel/laravel <target>.
  • It writes production .env values, prepares storage/, storage/logs/, and bootstrap/cache/, generates APP_KEY, runs migrations, clears optimization caches, marks the site runtime as Laravel, and reapplies runtime config.
  • If an existing site database is linked, known database name/user values can be written; Herne does not expose or invent stored database passwords.
  • After install, package products such as QuizTem can be installed through Composer or Terminal.

WebBlocks CMS Quick Install

The WebBlocks CMS installer prepares a Laravel-based CMS in the site's web_root project path.

  • Generated database credentials are created for the target site and written into the app environment.
  • The installer protects the panel database from being selected as the target application database.
  • .env values are written carefully so existing secrets are not overwritten unnecessarily.
  • APP_KEY is generated or preserved safely, depending on the current installation state.

Runtime Checks

The installer verifies that the target runtime can write the paths required by Laravel before it marks the app as installed.

  • Writable project paths are checked before finalization.
  • Partial installer files are cleaned up when a failed attempt can be safely retried.
  • Finality checks keep a successful install from being overwritten by a retry action.

Failed and Retry States

If an installation fails, the Apps page keeps the failed state and exposes logs. Use Retry Install after fixing DNS, database, permissions, or runtime issues.

A retry is designed to resume cleanly after partial cleanup. It should not be used to replace an already finalized production app.

After Install

  • Open the generated site URL and, for WebBlocks CMS, the admin URL from the Apps page.
  • Use Sites → .env for follow-up environment edits.
  • Run optimize:clear from the Artisan runner after manual environment changes.
  • Use Settings → SSL / HTTPS to re-sync certificates after adding aliases.