109
edits
Changes
Bugzilla:FAQ 7. Bugzilla and Win32
=[[Bugzilla:FAQ:General_Questions|General Questions]]=
=[[Bugzilla:FAQ:Managerial_Questions|Managerial Questions]]=
=[[Bugzilla:FAQ:Administrative_Questions|Administrative Questions]]=
=[[Bugzilla:FAQ:Bugzilla_Security|Bugzilla Security]]=
=[[Bugzilla:FAQ:Bugzilla_Email|Bugzilla Email]]=
=[[Bugzilla:FAQ:Bugzilla_Database|Bugzilla Database]]=
=[[Bugzilla:FAQ:Bugzilla_and_Win32|Bugzilla and Win32]]=
==What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?==
Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference. B^)
Seriously though, making Bugzilla work easily with Windows was one of the major goals of the 2.18 milestone.
If the necessary components are in place (perl, a webserver, an MTA, etc.)
then installation of Bugzilla on a Windows box should be no more difficult
than on any other platform.
As with any installation, we recommend that you carefully
and completely follow the installation instructions in
[http://www.bugzilla.org/docs/tip/html/os-specific.html#os-win32 Section 2.4.1].
While doing so, don't forget to check out the very excellent guide
to [http://www.bugzilla.org/docs/win32install.html Installing Bugzilla on Microsoft Windows]
written by Byron Jones. Thanks, Byron!
==Is there a "Bundle::Bugzilla" equivalent for Win32?==
Not currently.
Bundle::Bugzilla enormously simplifies Bugzilla installation on UNIX systems.
If someone can volunteer to create a suitable PPM bundle for Win32,
it would be appreciated.
== CGI's are failing with a "something.cgi is not a valid Windows NT application" error. Why?==
Depending on what Web server you are using,
you will have to configure the Web server to treat *.cgi files as CGI scripts.
In IIS, you do this by adding *.cgi to the App Mappings
with the <path>\perl.exe %s %s as the executable.
Microsoft has some advice on this matter, as well:
*"Set application mappings. In the ISM, map the extension for the script file(s) to the executable for the script interpreter. For example, you might map the extension .py to Python.exe, the executable for the Python script interpreter. Note For the ActiveState Perl script interpreter, the extension '.pl' is associated with PerlIS.dll by default. If you want to change the association of .pl to perl.exe, you need to change the application mapping. In the mapping, you must add two percent (%) characters to the end of the pathname for perl.exe, as shown in this example: '''c:\perl\bin\perl.exe %s %s'''"
== I'm having trouble with the perl modules for NT not being able to talk to the database.==
Your modules may be outdated or inaccurate. Try:
#Hitting http://www.activestate.com/ActivePerl
#Download ActivePerl
#Go to your prompt
#Type 'ppm'
#PPM> '''install DBI DBD-mysql GD'''
I reckon TimeDate and Data::Dumper come with the activeperl.
You can check the ActiveState site for packages for installation through PPM.
http://www.activestate.com/Packages/.
=[[Bugzilla:FAQ:Bugzilla_Usage|Bugzilla Usage]]=
=[[Bugzilla:FAQ:Bugzilla_Hacking|Bugzilla Hacking]]=
=[[Bugzilla:FAQ:Managerial_Questions|Managerial Questions]]=
=[[Bugzilla:FAQ:Administrative_Questions|Administrative Questions]]=
=[[Bugzilla:FAQ:Bugzilla_Security|Bugzilla Security]]=
=[[Bugzilla:FAQ:Bugzilla_Email|Bugzilla Email]]=
=[[Bugzilla:FAQ:Bugzilla_Database|Bugzilla Database]]=
=[[Bugzilla:FAQ:Bugzilla_and_Win32|Bugzilla and Win32]]=
==What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)?==
Remove Windows. Install Linux. Install Bugzilla.
The boss will never know the difference. B^)
Seriously though, making Bugzilla work easily with Windows was one of the major goals of the 2.18 milestone.
If the necessary components are in place (perl, a webserver, an MTA, etc.)
then installation of Bugzilla on a Windows box should be no more difficult
than on any other platform.
As with any installation, we recommend that you carefully
and completely follow the installation instructions in
[http://www.bugzilla.org/docs/tip/html/os-specific.html#os-win32 Section 2.4.1].
While doing so, don't forget to check out the very excellent guide
to [http://www.bugzilla.org/docs/win32install.html Installing Bugzilla on Microsoft Windows]
written by Byron Jones. Thanks, Byron!
==Is there a "Bundle::Bugzilla" equivalent for Win32?==
Not currently.
Bundle::Bugzilla enormously simplifies Bugzilla installation on UNIX systems.
If someone can volunteer to create a suitable PPM bundle for Win32,
it would be appreciated.
== CGI's are failing with a "something.cgi is not a valid Windows NT application" error. Why?==
Depending on what Web server you are using,
you will have to configure the Web server to treat *.cgi files as CGI scripts.
In IIS, you do this by adding *.cgi to the App Mappings
with the <path>\perl.exe %s %s as the executable.
Microsoft has some advice on this matter, as well:
*"Set application mappings. In the ISM, map the extension for the script file(s) to the executable for the script interpreter. For example, you might map the extension .py to Python.exe, the executable for the Python script interpreter. Note For the ActiveState Perl script interpreter, the extension '.pl' is associated with PerlIS.dll by default. If you want to change the association of .pl to perl.exe, you need to change the application mapping. In the mapping, you must add two percent (%) characters to the end of the pathname for perl.exe, as shown in this example: '''c:\perl\bin\perl.exe %s %s'''"
== I'm having trouble with the perl modules for NT not being able to talk to the database.==
Your modules may be outdated or inaccurate. Try:
#Hitting http://www.activestate.com/ActivePerl
#Download ActivePerl
#Go to your prompt
#Type 'ppm'
#PPM> '''install DBI DBD-mysql GD'''
I reckon TimeDate and Data::Dumper come with the activeperl.
You can check the ActiveState site for packages for installation through PPM.
http://www.activestate.com/Packages/.
=[[Bugzilla:FAQ:Bugzilla_Usage|Bugzilla Usage]]=
=[[Bugzilla:FAQ:Bugzilla_Hacking|Bugzilla Hacking]]=
