BugNET

Open source issue tracking & project management
Welcome to BugNET Register | Login |

BugNET Documentation

Installation

3

In this page you can find all the information about installing and configuring BugNET.

 

General BugNET Issues

Pre-installation System Requirements

  1. IIS Web Server 5 or later
  2. Microsoft .NET Framework v3.5 SP1 Redistributable
  3. Microsoft SQL Server or Microsoft SQL Server Express 2005 or later

Installing BugNET

  1. Unzip the latest BugNet install package to a folder (e.g c:\BugNet) of your choice. This is the required package to run the BugNet Issue tracker. For the full source code package, visit the BugNET website.
  2. Make sure you have created a virtual directory on your local IIS which points to the folder that you have extracted the files in step 1 (e.g C:\BugNet). (e.g the url should be http://localhost/BugNet)
  3. Using Windows Explorer, browse to the root folder of the website ( C:\BugNet by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.
    If using Windows 2000 - IIS5 - the {Server}\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website 
    If using Windows 2003 - IIS6 - the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and Change Control of the virtual root of your website
  4. Create a blank SQL Database (e.g db name 'BugNet') on your sql server. For the upgrade, before you take any action, please backup your database.
  5. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString property to match the database you created in step 4.
    <connectionStrings>
    	<clear/>
    	<add name="BugNET" connectionstring="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet" providername="" />
    </connectionStrings>
    
  6. Browse to http://localhost/BugNet/Install/Install.aspx (or the url of the virtual directory you have created in step 2).
  7. The installation process will now start.
  8. When completed, you may log in with the admin user account.
     Username: admin
     Password: password

That's it, your BugNet Issue tracker installation should be up and running at http://localhost/BugNet. For any installation problems, please visit the Support Forums.

Upgrading BugNET

To upgrade your BugNET installation please follow the instructions for the specific version you currently have installed.

Upgrading From Version 0.7.X

  1. Backup your existing installation of BugNet, your database and rename your web.config to web.config.bak.resources
    **NOTE: Be sure to rename the web.config with the resources extension or someone could potentially download your web.config file.
  2. Copy your entire BugNet folder to another location.
  3. Delete the existing files in your current installation with the exception of:
    • Your backup of the Web.config
    • Uploads directory and its contents (these are your attatchments!)
    • Your App_Data folder (if you are using sql express)
  4. Unzip the latest BugNet install package into your existing install directory.
  5. Copy your connection string from your previous Web.config to the new one.
  6. Copy your machinekey elements from your old Web.config to the new one.
  7. Copy the installation date appsetting from the old Web.config to the new one.
  8. Browse to http://localhost/BugNet/Install/Install.aspx to complete the upgrade.

Upgrading From Version 0.6.7

  1. Backup your existing installation of BugNet and your database.
  2. Unzip the latest BugNet install pacakge overtop of your existing install.
  3. Make sure that the current Admin account password is at least 7 characters long. If not, run this script replacing YourPasswordHere with the password you wish to use.
    UPDATE Users SET Password = `YourPasswordHere` WHERE UserName = `Admin`
    

  4. Make sure that all users have a unique email address, otherwise the upgrade will fail. Run this script to determine duplicates and fix them accordingly:
    SELECT email, COUNT(email) AS NumOccurrences FROM users GROUP BY email HAVING ( COUNT(email) > 1 )
    
  5. Unzip the latest BugNet install package to a folder (e.g c:\BugNet) of your choice. This is the required package to run the BugNet Issue tracker. For the full source code package, visit the BugNet website.
  6. Edit the Web.config file with a text editor of your choice. Find the BugNET connection string setting and change the connectionString property to match your database.
    <connectionStrings>
    	<clear/>
    	<add name="BugNET" connectionstring="server=MyServer;database=BugNet;uid=BugNet;pwd=BugNet" providername="" />
    </connectionStrings>
    
  7. Browse to http://localhost/BugNet/Install/Install.aspx (or the url of the virtual directory you have created in step 2).
  8. The upgrade process will now start.
  9. When completed you may log in as normal.

Known Issues

For a list of known issues please visit http://support.bugnetproject.com.

Version History

For a version history please refer to the change log.

Acknowledgements

Thank you to everyone that has reported issues, submitted patches and your continued support and interest in BugNET.



  Rating
Rate This Page: Poor Great   |  Rate Content |
Average rating:  3   
10020
12345
Number of Ratings : 3
  Comments
Add Comment
frank morgan
Missing steps that should have been clarified better:
- Creating bugnet login for the new database (as mentioned in the connectionstring)
- Alternate way of installing it with integrated security (as that should be the end users primary scenario in most cases i guess)

Thanks
Posted At 25-01-2010 04:42:14
Stefan
Some steps in this instructions are not quite clear.

"Installing ButNet", Topic 4: "Create a blank SQL Database". How do I do that? I have just installed SQL Server Express 2005 from this location: http://go.microsoft.com/fwlink/?linkid=65212. The only administration tool that is included is the "SQL Server Configuration Manager" which allows to select client protocols and start/stop the service. This is pretty useless.
Posted At 08-01-2010 06:14:27



 |  View Topic History  |