Heroku-PHP | Get started using PHP on Heroku

These are the general appliable steps of configuring an MVC-based web application. Presumed web server version for the settings below: Apache HTTP Server v2.4.

1) Block access to all directories and files:

First of all, in the config file of Apache, the access to all directories and files should be blocked by default:

Solved the problem with, what I think, is nothing more than a workaround.

The deploy process was complaining always about the require-dev dependencies, so I did:

• Moved all require-dev to require;
• Run composer update to refresh the composer.lock file;
• Pushed and tried the deploy again with success.

This solution was take for many people in other issues I read, I'm just describing step-by-step what was done to fix it. Still, I don't think it's the correct fix for this, after all the dev-dependencies shouldn't being installed on prod environment.

If your root route works, then it sounds like the app deployed fine. Did you upload a .htaccess file to explain the rewrite rules to Heroku? From the Slim Docs, you need something like:

It reads: PHP memory_limit is 4M Bytes, 4 megabytes, which I would call an obvious mis-configuration. Try to set a rather realistic value of about 128M ~ 256M. That instance overall only has 512M. KeepAlive barely affects the memory, but one may run out of ports (don't worry with 128 FPM worker processes)... maybe configure the server less restrictive once and then check with memory_get_usage(false) (used memory, not allocated memory) how much memory the script actually needs. Unless knowing that value it is difficult to know what the least possible value is.

Heroku says, that R14 means: Memory quota exceeded ...so these are probably 128 workers with 4M each, which is already the hard limit of 512M. Setting up less workers might be an option; adding more RAM might be an option. When not setting the value to 4M, this would be the default value of 128M; when setting it to -1 it would ignore that soft limit (which might help when testing).

It appears that you are trying to deploy a static website to Heroku but specifying the heroku/php builpack which expects, well… a PHP app.

Two possible ways of doing this:

Meet the requirements of the heroku/php webpack:

1. Have some PHP code. For example, an index.php file with a redirect, like:

2. Have a composer.json file, which can just be:

   {}

Use heroku-buildpack-static:

This is a custom webpack for serving static sites. A complete guide is available here, but the highlights are:

Here's the relevant error message:

The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths. at /app/vendor/laravel/framework/src/Illuminate/Encryption/Encrypter.php:43

It looks like your APP_KEY isn't set properly.

In development this would probably be set via your your .env file, which shouldn't be included in your repository. This file is just a convenient way of setting environment variables in development; Heroku supports environment variables natively via config vars.

Either generate a new APP_KEY or copy the one from your .env file and set it on Heroku by running

I had the same problem when I tried to deploy my test project in heroku recently. Lately I found out that there's a problem in my Procfile

/app is the absolute path on the file system, where you app resides. The error indicates that your Procfile does not actually contain what you claim it does. You probably haven't added and committed it to Git. Apache is trying to serve from the "root" right now, not from the public/ subdirectory.

Change to: