Timeline for TDD, configuration management, configuration patterns (PHP)
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2015 at 16:55 | answer | added | schellingerht | timeline score: 1 | |
| Aug 5, 2015 at 15:37 | answer | added | Tom B | timeline score: 0 | |
| Aug 5, 2015 at 14:50 | comment | added | JDT | If you don't want the config files overwritten, don't deploy them along with your app and just keep it on the server. That way you know the file is up-to-date, otherwise you risk a change being done in production and if the file is not copied back to wherever you store config files the thing blows up post-update. Treat config files as data and back them up. If the server crashes, get the config file from the backup. | |
| Aug 5, 2015 at 14:43 | answer | added | JDT | timeline score: 2 | |
| Aug 5, 2015 at 14:34 | vote | accept | Jayy | ||
| Aug 5, 2015 at 14:33 | answer | added | Jules | timeline score: 0 | |
| Aug 5, 2015 at 14:27 | answer | added | Jayy | timeline score: 0 | |
| Aug 5, 2015 at 14:24 | history | edited | Jayy | CC BY-SA 3.0 |
added 127 characters in body
|
| Aug 5, 2015 at 14:21 | comment | added | Cerad | Take a look at how the Symfony framework handles multiple environments: symfony.com/doc/current/cookbook/configuration/…. Might help to crystallize some things for you. | |
| Aug 5, 2015 at 14:20 | history | edited | Jayy | CC BY-SA 3.0 |
added 127 characters in body
|
| Aug 5, 2015 at 13:07 | history | edited | Jayy | CC BY-SA 3.0 |
added 307 characters in body
|
| Aug 5, 2015 at 12:54 | history | asked | Jayy | CC BY-SA 3.0 |