Welcome to the nuBuilder forums!

Please register and login to view forums and other content only available to registered users.

NEW Windows Install

Post Reply
pickle_jimmy
Posts: 38
Joined: Mon Jul 25, 2011 4:00 am

NEW Windows Install

Unread post by pickle_jimmy »

Woo Hoo...

It is a great day for the nuBuilder Windows Community, we have a new installer!

We have bundled nuBuilder with the UwAmp package - a very nice self contained WAMP stack. To use it - download the latest EXE (go to www.nubuilder.com for the link) and run it. Sounds too easy. Well, you might have to ensure that you don't have something running on port 80, but other than that, it will extract itself into (by default) the C:\uwamp directory, and run itself. From there the control panel allows you to pop open the default website, phpmyadmin, and the wwwroot dir - as well as change ini settings and start/stop the services.

The databases (sample and sampleNuFinancial) are already in phpmyadmin, the sites are set up, it is that simple.

Let me know if you have issues - otherwise; enjoy.

AMP Version Updates from last Windows Installer
Apache 2.2.11 -> 2.2.17
Mysql 5.1.34 -> 5.5.9
PHP 5.2.9 -> 5.3.5
PHPMyAdmin 3.1.4.0 -> 3.3.9.1

Cheers

Pickle Jimmy
quaxth
Posts: 31
Joined: Fri Jul 06, 2012 5:49 pm

Re: NEW Windows Install

Unread post by quaxth »

Looks good. Will test it under Windows 8 Enterprise 64bit and see how it works.

Just a stupid question: As Port 80 is may used for other apps etc. why not set the default in installer to an different Port, let say 18080 or something else?
pickle_jimmy
Posts: 38
Joined: Mon Jul 25, 2011 4:00 am

Re: NEW Windows Install

Unread post by pickle_jimmy »

Hi All,

Q. With the new installer, why did we choose to leave it using the default HTTP port of 80 rather than using an obscure port that would not have clashed with existing Web Servers running on the machine??

A. Very good question (SMIRK). Actually, it is VERY easy to change the port - and I will describe the process below for those that have a clash - but it does mean that it is not as straight forward to access the pages for the uninitiated. So, it came down to 1) Avoiding a 'Port Clash' and requiring the addition of a port number in the URL *OR* 2) Clashing on the odd occasion but avoiding everyone needing the URL Port thingy (Technical Term - sorry)

So, if you do have a clash - which you will know about because UWamp will tell you and you will not be able to start the Apache Service

1) There is a button on the UWamp interface called "Apache Config" - click it.
2) This will bring up a "Virtual Server" list on the left - select the virtual servers (Apache Main *:80 - AND - www.example.com *:80) one at a time, and on the right
hand side, (next to "Port:") change to port number to something other than 80 - eg 8080
3) Click OK
4) If you are doing this, it is probably because you had a clash, so you should now be able to start Apache (On the UWamp Interface, click the "Start" button)
5) When you click the "www Site" button, the URL will automagically be http://localhost:port/ (http://localhost:8080/ in my case)

Cheers

Pickle Jimmy

Answers to questions that nobody asked...
2a) Do not use port 20, 21, 25, 110, etc - infact, if you are not using port 80, then choose a port above 1024 and below 65535
2b) If you dont use 8080, read http://en.wikipedia.org/wiki/List_of_TC ... rt_numbers just to be on the safe side
Post Reply