Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to licence a non-trivial PHP application I have been working on under Affero GPL v3 (because I want every admin, who will use it, also release the source code).

However, something troubles me. I have a file localSettings.php, where the admin is supposed to write keys and some more information for MySQL database and some other secret info in the form


and so on.

BUT. Under the AGPL, if he changes this, isn't he obliged to release the changed source code together with the secret credentials? (Because the file localSettings.php is, too, licensed under AGPL.)

share|improve this question
up vote 2 down vote accepted

As the author (more strictly speaking, the copyright holder), you're entitled to license anything any way you want. Just declare in your license that the localSettings.php is licensed differently, and not subject to the Aferro GPL. Stuff like this is done all the time (e.g., the GNU Classpath exception) when then authors decide they want to allow exceptions to the license restrictions for whatever reason they want. Heck, you could offer an exception for any file dated on a Thursday, because you were born on a Thursday.

share|improve this answer
Oh. OK. This makes sense, thanks. – Karel Bílek Jan 25 '13 at 5:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.