Use environment files

[cachethq]

Use environment files

[jbrooksuk]

The problem with the application key being in the environment is on deploying to Heroku. There is no way to generate it there. I actually use a .env.local.php file when developing locally to set the environment when testing Heroku deployment before I push to master.

Heroku does use an environmental variable for the database settings too, see app/config/heroku/database.php.

If you have any suggestions on this, please make a PR.

[Ehesp]

I've never used Heroku, but I thought you could apply environment variables in the config file or dashboard from the site, as mention here.

'key' => $_ENV['APP_KEY'],

Then, if you're on Heroku or not you can just add an .env.php file and you're good to go too.

Either way, if someone were to clone and deploy the application as of now, then it would be unsafe if the key didn't change.

If someone can confirm the Heroku environment part, that'd be great.

[jbrooksuk]

Sorry, yes, we could do that, getenv('APP_KEY'). The problem is that the environment variable has to be set within app.json.

What we could do though is (at least for Heroku) add a postdeploy command for php artisan key:generate which will change it in the file.

Locally it won't make a difference so we'd have to advise generating it before deploying Cachet on your servers.

[jbrooksuk]

I've now set Heroku deployment to generate the app key again.