Pro Edition FAQ

Subscribe to Pro Edition FAQ 1 post, 1 voice

 
Avatar BenMcDonald 44 posts

Q1: When will Pro Edition be released?

A: Before the end of May.

UPDATE: Pro Edition has been released for General Availability as of Sept 12, 2007.


Q2: Is Pro Edition free?

A: You have a 30 day FREE TRIAL period.


Q3: What type of code can I add to my Index?

A: Any code you have access to. If you can check it out from a version controlled repository, you can index it.


Q4: Can you give me a sneak peak?

A: Sure. Just don’t tell anyone—Pro Demo


Q5: Who can I invite and share my Index with?

A: Anyone you like. Just be aware that you are making your source code accessible to others.


Q6: I sent an invite, but my friend didn’t receive it. What gives?

A: It’s possible that your invite was sent to their junk email folder. Hotmail, in particular, seems to have a distaste for our cordial requests. Ask the receiver to add koders.com to their list of trusted senders or, heaven forbid, give them a call!


Q7: I try to get to http://localhost:8080 and it says “Unable to connect”?

A: Check to be sure that the Koders Web Server is running. You can Stop and Start the service from the Setup screen in Kodebot—lower left-hand corner.


Q8: When I’m choosing my Project to index, should I select ‘trunk’ or the top level which includes all releases?

A: It’s really up to you. If you are just interested in the latest code, choose “trunk”. If you want to include code files from all past releases, choose the top level folder. However, be aware that you will get duplicate search results, if you decide on the latter.

Another option is to create separate Projects that correspond to your past releases. You could then scope your searches to a particular release, if you so desired.


Q9: Why don’t the links from Kodebot launch when I click them?

A: If you are using Firefox then most likely that is the problem. Firefox has a bug with how they handle Windows passing them a URL. You can read the bug report on Mozilla’s site…case 246078.


Q10: How do I configure my Koders IDE Plugin to search my internal code indexed by Pro?

Check out our blog post and video ... OR …

  1. In the IDE, make the main Koders Search panel visible and select the koders drop down menu item Options->Search
  2. Under the “General Search” tab, set the “Enterprise Server URL” option to point at your local Pro installation (e.g. http://192.158.3.10:8080/) and hit the TEST button to ensure that it can connect to the server.
  3. Set the SmartSearch Scope for Pro by selecting the SmartSearch tab and choosing the appropriate Scope option to either be “Enterprise Code” for Pro results only or “Both” for Pro and open source internet results from www.koders.com. Select OK to close the Options dialog
  4. Set the General Search Scope option, by selecting “All Languages, All Licenses, Open Source” from the main Koders Search Panel and choosing “Enterprise”.

Q11: Koders Pro is loading veeerrrry slowy using Firefox on Vista. What can I do?

A: This is an issue when pairing up Cassini with Firefox and Vista, but it has an easy fix.

  1. Type ‘about:config’ in the Firefox address bar
  2. Type ‘IPV6’ into the Filter
  3. Double-click on network.dns.disableIPV6 to change its value to ‘true’

Firefox will be back to its speedy self in no time.


Q12: How can I change the location of my Koders Pro Index?

A: Please follow these instructions:

  1. Stop the Koders Indexer service (KodeBot Setup screen, lower left)
  2. Stop the Koders Web Server service (KodeBot Setup screen, lower left)
  3. Exit KodeBot
  4. Open C:\Program Files\Koders\Professional\Configuration\KodeShare.config
  5. Create a new folder for your database files, say C:\Database
  6. Modify the path for <workingindexdb> to C:\Database\working.db3
  7. Modify the path for <liveindexpath> to C:\Database\KodeShareIndexLive_x.db3
  8. Modify the path for <statsdb> to C:\Database\stats.db3
  9. Exit and save KodeShare.config
  10. Move working.db3 and stats.db3 files from C:\Program Files\Koders\Professional\Database to your new database folder
  11. Start KodeBot and restart the Indexing and Web services
  12. Verify that you can successfully add new projects to the new index location

Q13: Why can’t KodeBot browse my repository even though I have Tortoise-SVN installed?

A: KodeBot launches Subversion from the command line, so it needs to be able to locate svn.exe. Tortoise-SVN doesn’t install svn.exe, so you’ll need to download it here. Also, be sure that you’ve modified your Environment Variables path to include the location of svn.exe. A reboot is required for this change to take effect.


Q14: If there are no changes in a particular project, will KodeBot spend time recrawling and indexing it?

A: Both crawling and indexing are incremental processes. Therefore, only changes that are detected require re-crawl and re-index. You may see a small amount of crawl and index time (< 1 min) as the system looks for changes, but this time should be significantly less than the initial task.


Q15: What type of relevancy/ranking system is used to generate search results?

A: Initial search algorithms are set to rank keyword frequency and location as the most significant factors. However, as your system experiences more use, user heuristics that take into account reuse are factored into the ranking of code files. Essentially, the more a code file is reused, the higher it can placed in the search results.


Q16: What is the advantage of a version control adapter plugin compared to the FileSystemAdapter?

A: Using a version control adapter for, say, CVS or Subversion allows KodeBot to connect directly to the repository, essentially eliminating the step of manually checking out code to the local box and then having KodeBot index it with the FileSystem Adapter. With a VCA, you are assured that KodeBot is always indexing the most up to date code from a repository. For a diagram of FSA, click here: http://www.koders.com/media/pro/docs/kodersguide_11.htm


Q17: Why can’t a person I shared my index with access it via their browser?

A: You may need to create a port exception in your Windows Firewall to allow outside access to your web server.

  1. Open Windows Firewall
  2. Click the Exceptions tab
  3. Click Add Port…
  4. Enter the Name as “Koders Pro”
  5. Enter the Port (default for Pro is 8080)
  6. Select TCP

If the above does not work, you may need to contact your system administrator to help.


Q18: Does KodeBot reindex on a scheduled basis?

A: Yes. The default schedule is daily at midnight. You can modify this schedule by editing the appropriate configuration file:

  1. Open C:\Program Files\Koders\Professional\KodeBot\KodeBot.exe.config
  2. Change “ReindexStartTime” to a new time value in 24-hr format
  3. Change “TimeBetweenReindexes” to a new value in d.hh:mm:ss format

Note: If you are utilizing the FileSystem Adapter, you will need to update your source code outside of KodeBot before reindexing to insure your index contains the most recent code.

For a more information about FileSystem Adapter, check out this help file.


Q19: Why do I get this error when launching Pro Search?

“Windows cannot find ‘C:\Documents and Settings\All Users\Desktop\Koders Pro Edition.url’. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.”

A: This is a known Firefox bug that occurs when FF is your default browser and you attempt to open an html file without having FF already running. You can click OK and FF should launch without issue.


Q20: How do I index a CVS project that has spaces in its name like My Spacey Project?

A: You can place single quotes around the %REMOTE_PATH% variable like so:

Repository Connection String:

-d:pserver:username:password@cvs.domain.com:/usr/local/cvsroot co ‘%REMOTE_PATH%‘

And then the string below will be passed to CVS:

-d:pserver:username:password@cvs.domain.com:/usr/local/cvsroot co ‘My Spacey Project’