•

If your server has more than one (non lo) IP you will need to bind Noodle to one of them for the license key to work.
Add the address to the connection In server.xml

Restart the service for changes to take effect.

•

Clearing the DNS cache on your computer:
windows:

ipconfig /flushdns

OS X:

dscacheutil -flushcache

linux:

/etc/init.d/nscd restart

You can't clear the cache on your ISPs DNS servers but you can use different servers (opendns, googledns, etc)

•

Noodle works with PostgreSQL and uses the contributions which are included in the windows installer but installed separately with package management systems like apt and yum.

before PGSQL-v9 will need:

CREATE LANGUAGE plpgsql;

All versions need a user, database and rights and the following to load the lo-manage triggers (the Noodle installer for Windows will do this for you):

ALTER USER noodleuser WITH SUPERUSER;

You will need these SQLs if you are upgrading from an old version.

•

Noodle uses 4 things on the server

  1. The Noodle folder (older versions are named IntraNet)
  2. The database folders (can be on a different server)
  3. The Java Folder
  4. Optional tools; ffmpeg, anything used by custom search filters, etc

On Windows the Noodle folder is in %PROGRAMFILES(x86)% by default.

On Linux the Noodle folder is in /opt/ by default.

Among other things the Noodle folder contains the following of potential interest:

  1. conf/server.xml (connection settings)
  2. conf/noodle.properties (application settings)
  3. logs
  4. optional files like MOTD.html/custom.js/noodle.jks

•

You need custom scripts enabled.

var doc=top.noodle.headWindow().document;
var el=doc.getElementById("helpLink");
el.style.fontSize="";
el=doc.getElementById("feedback");
el.style.fontSize="";
el=doc.getElementById("logout");
el.style.fontSize="";
el=doc.getElementById("logout").parentNode.parentNode;
el.style.fontSize="14px";

•

You need custom scripts enabled.

function HideFrames(){
this.hide=function(){
	this.navFrameSize=top.document.getElementById("lowerBody").cols;
	top.document.getElementById("lowerBody").cols="0,*";
	this.headFrameSize=top.document.getElementById("body").rows;
	top.document.getElementById("body").rows="0,0,*";
};
this.show=function(){
	top.document.getElementById("lowerBody").cols=this.navFrameSize;
	top.document.getElementById("body").rows=this.headFrameSize;
};
this.init=function(){
	var doc=top.noodle.headWindow().document;
	var cDiv=doc.getElementById("helpLink").parentNode.parentNode;
	var el = doc.createElement('a');
	el.innerHTML="hideFrames";
	el.href="#";
	el.className="whitelinks";
	top.noodle.cbc.addEventListener(el,"click",this.hide);
	cDiv.appendChild(el);
};
}
if(!top.noodle.hideFrames){
	top.noodle.hideFrames=new HideFrames();
	top.noodle.hideFrames.init();
}

•

Noodle will run on almost anything but we recommend the following setups:

Moderate dedicated server or VM only running operating system, Java, database, and Noodle:

  • 4GB RAM (1 for the OS 0.5 for Noodle and the rest for the RDBMS)
  • Dual core
  • 1TB drive space
  • 100mbps

Big configuration:

  • 2GB RAM + the size of your database
  • Quad core (any more cores will likely not be used)
  • AES-NI
  • software raid 0 (or SSDs)
  • 10mbps per user

An off site backup is recommended.

When using a VM shared IO can be a issue so be sure to verify your VM is getting the speed it needs.