RavenDB external config is being ignored -


ravendb's server (builds 2330 , 2380) seem ignore --config parameter:

raven.server.exe --config=another.config 

the feature has been suggested , confirmed , implemented. there constraints on location of configuration file?

in particular, cannot seem change port number unless overwrite existing configuration file raven.server.exe.config, rather specifying new configuration file using command-line option.

there appears strangeness in method used config. command line argument won't work 2.0 builds. fixed in 2.5

in meantime, can set values explicitly using:

raven.server.exe --set=raven/port==9999 

note first equal repeat once, , second repeat twice.


Comments

Popular posts from this blog

How to mention the localhost in android -

php - Calling a template part from a post -

c# - String.format() DateTime With Arabic culture -