Anvyr Docs
Documentation menu Anvyr Loom 1.x
Anvyr Loom

Version 1.x

← All documentation

GuideAnvyr Loom 1.xOperator

Deploy a Loom application

Prepare the runtime, serve the public entry point, and verify a release.

On this page

Prepare the release

Deploy your application code and its locked Composer dependencies. Run dependency installation from the application's root:

composer install --no-dev --no-interaction --prefer-dist

Confirm that the host meets installation requirements. An application using Markdown must declare its parser as a production dependency, not only a development dependency.

If Composer uses a local path repository, that path must also exist on the host. A package checkout on your development machine is not copied to production automatically.

Serve the public entry point

Point the web server's document root at the application's public/ directory. Configure unknown application paths to reach public/index.php, while serving existing public files normally.

Keep user/, storage/, configuration files, and Composer dependencies outside the public document root. Use a production PHP runtime such as PHP-FPM; loom serve is a development server.

Configure the production process

Set the application environment and disable debug output. Verify effective values in your application instead of assuming a particular bootstrap loads .env.

php loom config:get app.env
php loom config:get app.debug

Ensure the PHP process can write the configured storage and cache directories. If the application uses a database, apply its migrations as a deliberate deployment step. Restart long-running queue workers when changing application code.

Refresh derived state

php loom cache:clear
php loom config:clear
php loom index:rebuild
php loom page:list

Check the discovered pages, including nested content. Compile configuration or routes only when your deployment process manages their invalidation and rebuilds.

Verify the release

Request the home page, a nested content page, an application route, and a static asset. Check an unknown URL returns 404 and a draft page is hidden. Inspect logs for errors and check the web runtime's effective environment if CLI and HTTP behavior differ.

Keep a previous working release and a rollback procedure appropriate to your data changes. A code rollback does not undo a database migration automatically.

Continue readingWhy is my page missing?