Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Fitzchak Yitzchaki commented on Fix it in the code, not in the documentation@James, It's actually very simple. You have two options here: 1. Explicitly specify the port that you want. If you do so, that's the port that Raven.Server is going to use. If it can't use it, an exception will be thrown. 2. Use the star value (`"*"`) which will let Raven.Server to automatically choose a port that is free to use. In this case, we'll start looking for port number 8080 and increase the port number until a free port is found. This option will give you more flexibility in development environments. You can set this setting in the `Raven.Server.exe.config` file: <add key="Raven/Port" value="*"/> http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment11http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment11Wed, 08 Jun 2011 20:36:02 GMTJames commented on Fix it in the code, not in the documentationUgh. That's complicated. Now I have to remember all these things: 1. It will swap ports if 8080 is already in use 2. BUT - this feature only kicks in if explicitly set in config 3. BUT! The default config has this explicitly set! 4. Also, I have to remember to take it out for production config! And to top it off, it's not in documentation, so to recall these 4 points I have to wade through code! Too much magic. Why don't you just have a port variable in the config. Let the user choose; don't assume you know what they want. http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment10http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment10Wed, 08 Jun 2011 08:55:18 GMTFitzchak Yitzchaki commented on Fix it in the code, not in the documentation@Robert @Matthew, Take a look [here](http://blog.hibernatingrhinos.com/5/ravendb-in-practice-part-1-an-introduction-to-ravendb), specifically in [this](http://blog.hibernatingrhinos.com/images/blogs_hibernatingrhinos_com/Windows-Live-Writer/An-introduction-to_8C2C/clip_image002_2.png) picture. As you can see, the console application specifies the `Server Url` and `Port` values.http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment9http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment9Mon, 06 Jun 2011 18:07:01 GMTRobert commented on Fix it in the code, not in the documentationI agree with Matthew; how is the client made aware of the auto-chosen port?http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment8http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment8Mon, 06 Jun 2011 12:50:20 GMTAyende Rahien commented on Fix it in the code, not in the documentationRafal, That assumes: a) That your client has VM software and is willing to run it. b) That scares people off because they assume that your software must be very hard to configure. c) If you are using a Windows VM, you have licensing issues. http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment7http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment7Mon, 06 Jun 2011 11:52:35 GMTAyende Rahien commented on Fix it in the code, not in the documentationJB, You mean like HTTP Alternate when you are writing HTTP server? That sounds like an excellent choice to me, the reason that we choose that port was to allow easier support for proxies and firewalls.http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment6http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment6Mon, 06 Jun 2011 11:51:14 GMTTommaso Caldarola commented on Fix it in the code, not in the documentationA bad choice!http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment5http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment5Mon, 06 Jun 2011 09:58:45 GMTRafal commented on Fix it in the code, not in the documentationIMHO one of the best things to do if you want to make initial user experience as painless as possible is to provide a virtual machine appliance. Without it I wouldn't even try to set up some 'exotic' products like SOLR, Kannel, ejabberd and many other - because of the pain of going manually through the installation process. You may, however, have some problems with handing out Windows VMs... http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment4http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment4Mon, 06 Jun 2011 07:39:41 GMTstephane commented on Fix it in the code, not in the documentationinteresting. Like most of the truths, it seems obvious once you hear it. That doesn't applies only to developer tools like RavenDB. We are building a cms for the publishing industry. If you can setup a demo in a finger snap for a client and never meet this kind of configuration conflict, that can only help the decision process :).http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment3http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment3Mon, 06 Jun 2011 06:31:54 GMTJB commented on Fix it in the code, not in the documentationShouldnt you fix it so it doesn't clash with a Well Known Port? http://www.iana.org/assignments/port-numbers Either register a port with IANA (still doesn't fix the issue if someone else is not playing nice) or use the private range >= 49152.http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment2http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment2Sun, 05 Jun 2011 22:02:01 GMTMatthew commented on Fix it in the code, not in the documentationUnless the client can somehow detect which port the server is running on, I'm not convinced this is actually a success maker. You've just moved the problem to first run of the client failing mysteriously. http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment1http://ayende.com/12289/fix-it-in-the-code-not-in-the-documentation#comment1Sun, 05 Jun 2011 13:58:19 GMT