WORK-IN-PRO= GRESS
This page will list many potential problems and gotchas that you may enc= ounter while installing, configuring, and running eZ Platform. If you stumb= le upon an obstacle, take a look here to see if your case isn't covered. Wa= nt to add to this page? Check out our instructions for co= ntributing to our documentation.
If you're having difficulty completing installation on a system with lim=
ited RAM (1GB or 2GB, for example), check that you've enabled swap. This al=
lows your Operating System to use the hard disk to supplement RAM when it r=
uns out. Running `php -d memory_limit=3D-1 app/console ezplatform:ins=
tall --env prod clean` on a system with swap enabled should yield su=
ccess. When a system runs out of RAM, you may see `Killed` when trying to c=
lear the cache (e.g., `php app/console --env=3Dprod cache:clear` from your =
project's root directory).
To make use of PlatformUI, you need to define the maximum upload sizeto = be consistent with the maximum file size defined in the Content Type using = a File, Media or Image Field Definition.
This is done by setting LimitRequestBody for Apache or
For instance, if one of those Field definitions is configured to accept =
files up to 10MB, then client_max_body_size (in case of Nginx)=
should be set above 10MB, with a safe margin, for example to 15MB.
If you accepted all the defaults when doing a `composer install`, but re= alize you need to go back and change some of those options, look in `app/co= nfig/parameters.yml` =E2=80=93 that's where they're stored.