BE: Removal of stdout.log

docs/API_LOGS.md

@@ -12,14 +12,13 @@ Only specific, pre-approved log files can be purged for security and stability r
 
 **Query Parameter:**
 
-* `file` → The name of the log file to purge (e.g., `app.log`, `stdout.log`)
+* `file` → The name of the log file to purge (e.g., `app.log`)
 
 **Allowed Files:**
 
 ```
 app.log
 IP_changes.log
-stdout.log
 stderr.log
 app.php_errors.log
 execution_queue.log

docs/API_OLD.md

@@ -352,7 +352,6 @@ This API endpoint retrieves files from the `/tmp/log` folder.
 | `report_output.json`     | JSON format report output                                     |
 | `report_output.txt`      | Text format report output                                     |
 | `stderr.log`             | Logs of standard error output                                 |
-| `stdout.log`             | Logs of standard output                                       |
 
 
 ## API Endpoint: /config files

docs/DOCKER_COMPOSE.md

@@ -170,6 +170,7 @@ However, if you prefer to have direct, file-level access to your configuration f
 ```
 
 **After (Using a Local Folder / Bind Mount):**
+
 Make sure to replace `/local_data_dir` with your actual path. The format is `<path_on_your_computer>:<path_inside_container>:<options>`.
 
 ```yaml

docs/PLUGINS_DEV.md

@@ -352,7 +352,7 @@ See: [UI Components](PLUGINS_DEV_UI_COMPONENTS.md)
 - **Settings Helper:** `/app/server/helper.py` - Use `get_setting_value()` in scripts
 - **Example Plugins:** `/app/front/plugins/*/` - Study working implementations
 - **Logs:** `/tmp/log/plugins/` - Plugin output and execution logs
-- **Backend Logs:** `/tmp/log/stdout.log` - Core system logs
+- **Backend Logs:** `/tmp/log/app.log` - Core system logs
 
 ---
 

docs/PLUGINS_DEV_DATASOURCES.md

@@ -364,7 +364,7 @@ sqlite> SELECT ... ;
 
 ```bash
 # Watch backend logs
-tail -f /tmp/log/stdout.log | grep -i "data_source\|MYPREFIX"
+tail -f /tmp/log/app.log | grep -i "data_source\|MYPREFIX"
 ```
 
 ---

docs/PLUGINS_DEV_DATA_CONTRACT.md

@@ -245,7 +245,7 @@ cat /tmp/log/plugins/last_result.YOURPREFIX.log | awk -F'|' '{print NF}' | sort
 
 **Check core processing in logs:**
 ```bash
-tail -f /tmp/log/stdout.log | grep -i "YOURPREFIX\|Plugins_Objects"
+tail -f /tmp/log/app.log | grep -i "YOURPREFIX\|Plugins_Objects"
 ```
 
 ## See Also

docs/PLUGINS_DEV_QUICK_START.md

@@ -143,7 +143,7 @@ ls -la /tmp/log/plugins/last_result.MYPLN.log
 cat /tmp/log/plugins/last_result.MYPLN.log
 
 # Check backend logs for errors
-tail -f /tmp/log/stdout.log | grep "my_plugin\|MYPLN"
+tail -f /tmp/log/app.log | grep "my_plugin\|MYPLN"
 ```
 
 ## Next Steps
@@ -162,7 +162,7 @@ Now that you have a working basic plugin:
 |-------|----------|
 | "Module not found" errors | Ensure `sys.path` includes `/app/server` and `/app/front/plugins` |
 | Settings not appearing | Restart backend and clear browser cache |
-| Results not showing up | Check `/tmp/log/plugins/*.log` and `/tmp/log/stdout.log` for errors |
+| Results not showing up | Check `/tmp/log/plugins/*.log` and `/tmp/log/app.log` for errors |
 | Permission denied | Plugin runs in container, use absolute paths like `/app/front/plugins/...` |
 
 ## Resources

docs/PLUGINS_DEV_SETTINGS.md

@@ -507,7 +507,7 @@ mylog('none', f"Setting value: {value}")
 Check backend logs:
 
 ```bash
-tail -f /tmp/log/stdout.log | grep -i "setting\|MYPLN"
+tail -f /tmp/log/app.log | grep -i "setting\|MYPLN"
 ```
 
 ## See Also