On Tue, 15 Feb 2011, Alvaro Lopez Ortega wrote:
On 15/02/2011, at 04:42, Tom Browder wrote:
But the cherokee-admin is very easy to use. However, I do wish one
could use it on a local host with path names that don't exist so one
can generate a config file for a remote host.
Even though it is not a really common use-case, I think it makes sense to
support it.
However, I'm not quite sure about how it should be implemented. Those errors
could be turned into warning, for instance.. or the tests just skipped whenever
cherokee-admin is launch with a certain parameter. Proposals? Ideas? Thoughts?
The current problem is actually Cherokee admin _not_ being totally
conservative regarding 'local broken paths' in the configuration file, yes
there are the 'red errors' but if paths are not filled in at all, nothing
'warns'.
I guess the best idea would be to start the admin with:
--make-non-existed-paths-non-fatal-warnings
This could make the 'red messages' disappear or maybe even go away
permanently. In the general case the 'Save' button should warn regarding
paths or sources not filled in, this should happen too for the 'remote'
usecase.
Stefan
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
