Skip to content
This repository was archived by the owner on Feb 22, 2024. It is now read-only.

Windows Installation Guide (beginners)

retobg edited this page Nov 5, 2012 · 9 revisions

Introduction

In this section you will learn how to set up a local test site / development environment on your Windows PC.

Steps to take

You need to do two things on your computer:

  • Install the software that Fusepool Platform needs in order to run
  • Retrieve Fusepool Platform source code
  • Build and run the platform

Install and configure required software

JDK and Netbeans

Get Java Development Kit with NetBeans (includes Apache Maven) Install JDK 6 Update 37 with NetBeans 7.2.1 (currently proven version)

http://www.oracle.com/technetwork/java/javase/downloads/jdk-netbeans-jsp-142931.html

GitHub for Windows

You can either install the closed source GitHub for windows from

http://windows.github.com/ This was you can clone the fusepool-platform via its gui. Or install and configure various open source software components as described below.

Putty

Install PUTTY

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Generate public and private key pair to be able to retrieve and commit code to Fusepool on GitHub

Run puttygen located in PUTTY folder (might be in the C:\Program Files (x86)\Putty folder) C:\Program Files\Putty\puttygen

In PuTTY Key Generator, select 'SSH-2 RSA' from Parameters on bottom and click 'Generate' (move mouse to speed up process)

Save private key (*.ppk file) for future use and copy public SSH key.

Load the SSH key into the putty agent

Now double click the .ppk private key file (or start pagent.exe in the putty folder and select the ppk file manually)

Give public part of the SSH key to GitHub

Enter public SSH key (copied from puttygen) to your GitHub account under 'SSH Keys'

https://github.com/settings/ssh

Windows Git client

Install msysgit (Git for windows) to clone Fusepool platform from GitHub (command line GIT only)

http://code.google.com/p/msysgit/downloads/detail?name=Git-1.8.0-preview20121022.exe

Set environment variable

Setup an environment variable to let Git now which ssh agent to use. If you are unsure how to edit environment variables see: http://support.microsoft.com/kb/310519 add this variable.

Assuming that you installed putty to its default location. Set the GIT_SSH environment variable like so: GIT_SSH=C:\Program Files\PuTTY\plink.exe

Install SmartGit for GUI to command line GIT (optional)

http://www.syntevo.com/smartgit/quick-start.html

Clone GitHub Fusepool platform on your PC.

From GitHub Fusepool platform, select 'ssh' from the URL choices on top of page git@github.com:fusepool/fusepool-platform.git

Now open up either the git bash or git shell depending on what you have chosen during installation of msysgit. Within the git shell run these commands (alternatively do these steps using SmartGit):

browse (using cd) to the location where you want to checkout the source code.

git clone git@github.com:fusepool/fusepool-platform.git
cd fusepool-platform
git submodule init
git submodule update

Build the code

Troubleshooting

Authentication issues on GitHub

  • Make sure your key is loaded in putty agent
  • Make sure you provided the public part of your key to GitHub
  • Make sure the GIT_SSH environment variable is setup and pointing to an existing plink.exe

Write errors during compilation

  • We have seen AVG antivirus exclusively opening files while maven tries to access them. Try (temporarily) disable the anti virus software.

The server's host key is not cached

Problem:

The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48
Connection abandoned.
fatal: The remote end hung up unexpectedly

fix: To add github.com to the known hosts we can open putty.exe and connect to github.com. Putty will pop up a window and ask you if you want to add the server's key fingerprint to the cache. Press yes here. At this point you can close down putty, we only started this to add the key to the cache.

Now try again with git.