To keep my config file on deploys but ignore my actual license in the repo, I chose to create a separate license.php:
//license key
c:set('license','K2-PRO-XYZ');
whereas the original config.php calls this via include():
@include 'license.php';
Ok for @bastianallgeier?
This touches the topic of security, e.g. leaving critical credentials in public code.
That’s is totally fine and not a bad idea at all - i actually do something similar 
I also do something similar.
Totally fine!! I was also thinking about adopting Laravel’s .env file for that or to use something similar.
… arrgh, nobody found the error! It has to be a string like
@include 'license.php';
of course. Sorry – better late than never. @Editors: Maybe edit the first post accordingly.