Commit graph

11 commits

Author SHA1 Message Date
2a391f4e0a Task: #53687 Simplify cfg argument handling and keep --siteDir with JSON write input (-i) 2026-03-26 12:27:12 +01:00
29d1da4ac5 Task: #53687 Align cfg brace style to project conventions 2026-03-26 12:10:55 +01:00
227de9ac07 Task: #53687 Replace --site/--directory-name with --siteDir and add JSON batch input
- Changed site targeting from --site, --directory-name, --directoryName to --siteDir
- Added write -i <json> for multi-setting input
- Added support for inline JSON string values in write
- Updated help/examples to generic placeholders
- Extended tests for new arguments and validations (all passing)
2026-03-26 11:28:58 +01:00
adf5a98768 Task: #53687 Handle missing mode fallback and add no-mode cfg tests 2026-03-26 10:10:26 +01:00
2737ec1d65 Task: #53687 Support instance-specific cfg write targets and add coverage 2026-03-26 10:10:26 +01:00
82346bc36f output errors to STDERR 2023-09-21 09:17:26 +02:00
b9ab345946 add isset check 2022-11-23 11:18:42 +01:00
097ca9444f add mode switch to cfg script 2022-11-23 08:10:40 +01:00
849b35a72a do not quote result if it is a single value 2022-11-07 12:07:59 +01:00
9457987a31 Settings files are no longer required
all you need is a config/ directory under the appPath
If you do not have any settingsfiles to read, show will always report
settings not found
If you write, you can only write a new file with settings in the root
like `cfg write PREFIX
='{"key":"value","key2":{"some":"more","levels":"there"}}'

Which will give you a file `config/PREFIX.conf.php` with the contents
``` php
<?php return
[
	'key' => 'value',
	'key2' =>
	[
		'some' => 'more',
		'levels' => 'there'
	]
];
```

If you have a `default.conf.php` but now `conf.php` and modify a setting
a new conf.php file with the setting to override is written
2021-05-05 08:52:34 +02:00
ab736148c0 implement beta version of cli
relates to #2268
2021-05-04 17:55:29 +02:00