Table of Contents

Running the application

Summary

How to run Dotkernel Light locally on AlmaLinux 10 under WSL 2, and how to recover from a stale config cache.

Details

We recommend running the application on AlmaLinux 10, using WSL 2:

  • if you don't already have:
  • install the application in a virtualhost as recommended by the chosen distro
  • set $baseUrl in config/autoload/local.php to the address of the virtualhost
  • give the web server write access to the data and log folders
sudo chown -R "$USER":www-data data log
sudo chmod -R 775 data log
  • run the application by opening the virtualhost address in your browser

You should see the Dotkernel Light welcome page.

If you are getting exceptions or errors regarding some missing services, try running the following command:

composer clear-config-cache

Do not run this with sudo. Doing so leaves the regenerated data/cache/config-cache.php owned by root, which the application can no longer rewrite — the permission errors the FAQ exists to fix.

If data/cache/config-cache.php is present, that config will be loaded regardless of the ConfigAggregator::ENABLE_CACHE configuration in config/autoload/mezzio.global.php

FAQ

Q: Which folders does the web server need write access to? A: data and log, owned by your user with group write access for the web server's group.

Q: What should I do if I get errors about missing services? A: Run composer clear-config-cache — without sudo — to clear the stale config cache.

Q: Why shouldn't I run composer clear-config-cache with sudo? A: It would leave the regenerated data/cache/config-cache.php owned by root, which the application can no longer rewrite.

On this page