Cover of the book Symfony 5: The Fast Track

Symfony 5: The Fast Track is the best book to learn modern Symfony development, from zero to production. +300 pages in full color showing how to combine Symfony with Docker, APIs, queues & async tasks, Webpack, Single-Page Applications, etc.

Buy printed version
Buy PDF version
  1. Home
  2. Documentation
  3. Setup
  4. Setting up or Fixing File Permissions
WARNING: You are browsing the documentation for Symfony 5.0 which is not maintained anymore. Consider upgrading your projects to Symfony 5.1.

Setting up or Fixing File Permissions

5.0 version
Maintained
3.4 4.4 5.1 current 5.2 master
Unmaintained
2.7 2.8 3.0 3.1 3.2 3.3 4.0 4.1 4.2 4.3

Setting up or Fixing File Permissions

In Symfony 3.x, you needed to do some extra work to make sure that your cache directory was writable. But that is no longer true! Since Symfony 4, everything works automatically:

  • In the dev environment, umask() is used in bin/console and public/index.php so that any created files are writable by everyone.
  • In the prod environment (i.e. when APP_ENV is prod and APP_DEBUG is 0), as long as you run php bin/console cache:warmup, no cache files will need to be written to disk at runtime. The only exception is when using a filesystem-based cache, such as Doctrine’s query result cache or Symfony’s cache with a filesystem provider configured.
  • In all environments, the log directory (var/log/ by default) must exist and be writable by your web server user and terminal user. One way this can be done is by using chmod -R 777 var/log/. Be aware that your logs are readable by any user on your production system.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.