Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




FullGeminiURL -- For what is it used?

web-app

We recently setup Gemini on a server in our network, under the ip address of 192.168.0.50. We also have this machine exposed on our DMZ to the Internet under a public IP Address.

When initially setup, the web.config had the FullGeminiUrl setup as 192.168.0.50. This caused internal users to access the Gemini site and issues fine; external access, however, was problematic where one could log into the Gemini site, but each of the issues were still having http://192.168.0.50... as the URL.

When I tried changing the FullGeminiURL variable to the value of the external IP address, the opposite problem occurs -- those accessing the system intenally were getting incorrect URL's for the issue links.

When I comment out the FullGeminiURL variable from the web.config, acces to the issue URL's seems to work fine -- external users see the external IP address as part of the URL, and the internal users see 192.168.0.50 as part of the URL.

Is FullGeminiURL required? It seems not as the site is running without it. I tried search the .pdf documentation file, but this variable is not mentioned in there. Will I see consequential effects by having this variable commented out of my web.config?

Thanks in advance for any information on this.

Mark Jordan

Mark Jordan, MCSD for .NET
Senior Software Engineer
NuSoft Solutions (www.NusoftSolutions.com)
Microsoft Gold Certified Partner
Grand Rapids, Michigan
Office: 616.954.9556 x 137
Fax: 616.954.7970
Email: mjordan@NusoftSolutions.com
markjjordan
· 1 		markjjordan
Friday, June 16, 2006, 2:26:16 PM
Replies (5)
helpful
0
not helpful

This is used for some site navigation. If you do not have it or it is incorrect you might experience problems when creating issues.
Mark Wing
· 9108 		Mark Wing
Tuesday, June 20, 2006, 11:13:13 AM
helpful
0
not helpful

Hi,

This inconsistence in the use of relative / full urls for gemini's links is a big problem for us. We have two differents url access on the same server, for some reasons, like :

http://domainname/gemini/main.aspx for some users
and
http://domainname:64220/gemini/main.aspx for others, because of some network issues.

FullGeminiURL is set to http://domainname/gemini/main.aspx, and for users that use http://domainname:64220/gemini/main.aspx some links don't work, like the links you have in the main issue view. Today, those users are rewriting those links themselves, wich is quite uncomfortable :(

Will this issue be solved, is there any workaround available ?

PS: Please excuse my english


mpicot
· 1 		mpicot
Wednesday, June 21, 2006, 5:20:38 PM
helpful
0
not helpful

This issue will be addressed with 2.1 release.

There is no workaround at the moment. You can put it as ~/ but then images will not be displayed.
Saar Cohen
· 5000 		Saar Cohen
Wednesday, June 21, 2006, 11:13:38 PM
helpful
0
not helpful

For what it's worth for whomever is also having this problem... the way we got around this was to use a domain specification instead (ie. gemini.ourCompanyDomainname.com). We then setup a DNS setting on ourCompanyDomainName.com so that gemini.ourCompanyDomainname.com pointed the external IP address. For our internal network, we setup our internal DNS to return the internal IP address (ie. 192.168.0.50) for gemini.ourCompanyDomainname.com.

Thus, internal access to gemini.ourCompanyDomainname.com would return 192.168.0.50, and external access to the same domain would give the external IP address.

Finally, in the web.config, we set the FullGeminiURL key variable to the domain name of gemini.ourCompanyDomainname.com.

All is functioning fine now with this workaround.
markjjordan
· 1 		markjjordan
Thursday, July 6, 2006, 3:56:59 AM
helpful
0
not helpful

Another workaround for this problem would be to install the gemini web application twice but connect both to the same database. This allows to have different settings for the two installations.
mbischoff
· 1 		mbischoff
Friday, July 28, 2006, 11:30:40 AM