Timeline for Global State, How To Do IT?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17 at 20:30 | comment | added | freakish | It's not about security but separation of concerns. You make config a source file, and then people keep adding stuff there. Including file i/o or even network i/o. Because you have Python, then why not? And then you have a mess, for example impossible to develop locally. Do not trust developers if you can enforce good standards. | |
| Jun 17 at 20:16 | comment | added | PythoonNoob9000 | i see it easier to but it in a source file, because i will import those config files into 1 source file anyways, this is just a simple template, so security isn't a big concern here | |
| Jun 17 at 19:56 | vote | accept | PythoonNoob9000 | ||
| Jun 17 at 14:29 | answer | added | JimmyJames | timeline score: 2 | |
| Jun 17 at 9:15 | answer | added | Arseni Mourzenko | timeline score: 5 | |
| Jun 17 at 6:15 | review | Close votes | |||
| Jun 22 at 3:03 | |||||
| Jun 17 at 5:35 | comment | added | freakish | Do not keep configuration in source code. Keep it in a separate data file, json or yaml or xml, or whatever (but not in Python). But separated from the app. Because you don't want to put code there, it just leads to mess. I blame Django for popularizing this anti pattern. | |
| S Jun 17 at 1:33 | review | First questions | |||
| Jun 17 at 14:34 | |||||
| S Jun 17 at 1:33 | history | asked | PythoonNoob9000 | CC BY-SA 4.0 |