This article aims to answer the frequently asked questions on the technical configuration of FogBugz On-Premises installations.
|
Can we configure the IIS service with virtual name redirects/proxies to enable site aliases? |
|
Regarding site redirection: Yes, it is supported by FogBugz. For site aliases, keep in mind that we can have two different FogBugz instances/databases running on the same machine and handled by the same IIS site. So each instance will get a different name (for example, site1.myfogbugz.com and site2.myfogbugz.com). If the user tries to type site3.fogbugz.com in a browser, FogBugz will respond with "Account Not Found!" message. This scenario can be configured with a Rewrite rule in IIS. |
|
Can we run multiple instances? |
|
Yes, as mentioned above, we can have two or more different FogBugz instances/databases running on the same machine and handled by the same IIS site (or even running on different machines and handled by different IIS sites). |
|
Does this mean that we could run two IIS sites connecting to different databases? |
|
Yes, the ideal scenario is to have one instance for bug tracking/project mgmt, etc. and then have a second site for customer support tickets with some people having a user on both sites. |
|
What constitutes a unique user, and how does the user aggregation work? |
|
A unique user or FogBugz instance requires the same Machine ID and Computer name to be entered for the product to be activated. If either of these values changes, then a new license will need to be generated by Support. |
|
Can multiple instances run from the same Windows IIS & SQL Servers? |
| Yes. |