Entering a license info in config.php used to do pretty much nothing, so we didn’t have any incentive to actually do it. Now in Kirby 2.1 a message is displayed in the Panel if you don’t enter a valid license, so you kinda have to do it, as it would not look serious if your clients saw it all the …

Good idea :smile: and thanks for sharing, but it remains annoying if you want to deploy from that repo as well … then you have to remember to copy the license file separately …

Yes, but you may have to do it only once, not for every deployment. It depends how you manage your servers and repo though.

Ha, nice I didn’t know about the @ operator. Digging a little bit, it doesn’t seem to have only fans: Five reasons why the shut-op operator (@) should be avoided

Sorry for the threadomancy :skull: Hi @Malvese , I love what you did here. Really could use that for a project I started working on, especially with other stuff like plugin keys etc. Anyway… I can’t get it to work, I think I’m not getting the $license path right in config.php, the panel can’t find …

We do this in a different way. For us the license is deployed in a JSON file from our puppet system. Then during deployment, we read the JSON file and update a placeholder in the configuration file with the license code. echo "Installing kirby license from server file" LICENSE=`cat ${TWOUP}/kirby…

Mh I haven’t tried a multisite install yet… With such a folder structure I’d try something like: $license = __DIR__ . DS . 'multisites' . DS . $multisite . DS . 'config' . DS . 'license.php'; if (file_exists($license)) { include $license; } (totally untested)

The issue I see here is that you are using a variable in the config.php ($multisite) that is not known there because it is defined in the site.php… You probably have. to get the folder name from $_SERVER_ $multisite = server::get('server_name');

Right, although after a few tries I still can’t get the path to work. Dunno if that’s related but I accidentally also found out that a custom panel stylesheet in config.php isn’t responding either. So maybe there’s even a larger error behind the whole multi-site setup which I’m trying to figure out …

[image] NECKRHINOS: The easiest and fastest way would be a config file for each seperate domain/ site. But… meh :slight_smile: I would have thought it os possible to have individual config files for each. domain? Would make a. lot of sense, not only for the license files.

License in config.php and deployment

The CMS Questions

phi53 May 22, 2015, 8:16am 4

I do the same, with @ instead of the if:

@include __DIR__ . DS . 'license.php';

What folders/files should I hide from public repo?

Topic		Replies	Views
Config.php structure Solutions v2	3	2716	August 25, 2015
Kirby multiple websites questions Questions v3	21	1419	December 20, 2022
License, multiple domains, one CMS instance Questions v3	26	1973	June 26, 2025
Use license for staging, test and production Questions	3	1112	March 25, 2021
Panel, Custom Config Path Questions v2	7	872	May 4, 2017

License in config.php and deployment

Related topics