Test Server Installation and Configuration - Revision history

James: /* Determining the CPU Type */

2014-02-09T07:27:44Z

Determining the CPU Type

← Older revision		Revision as of 07:27, 9 February 2014
Line 12:		Line 12:
	Most modern CPUs are 64-bit.		Most modern CPUs are 64-bit.

	These instructions have not been tested on a 32-bit machine. However, they should work with minimum changes. If you are planning to install on a 32-bit machine, you should download the x86 image: http://releases.ubuntu.com/precise/ubuntu-12.04.3-server-i386.iso		These instructions have not been tested on a 32-bit machine. However, they should work with minimum changes. If you are planning to install on a 32-bit machine, you should download the x86 image: http://releases.ubuntu.com/precise/ubuntu-12.04.4-server-i386.iso

	== Create Bootable Media ==		== Create Bootable Media ==

James: /* Create Bootable Media */

2014-02-09T07:26:57Z

Create Bootable Media

← Older revision		Revision as of 07:26, 9 February 2014
Line 16:		Line 16:
	== Create Bootable Media ==		== Create Bootable Media ==

	# Download Ubuntu Server 12.04.3 LTS 64-bit: http://releases.ubuntu.com/precise/ubuntu-12.04.3-server-amd64.iso		# Download Ubuntu Server 12.04.4 LTS 64-bit: http://releases.ubuntu.com/precise/ubuntu-12.04.4-server-amd64.iso
	# Determine if you will be writing the ISO file to a CD or a USB drive.		# Determine if you will be writing the ISO file to a CD or a USB drive.
	## CD: simply write the ISO image to a writable CD. Detailed instructions are available here for many operating systems: https://help.ubuntu.com/community/BurningIsoHowto		## CD: simply write the ISO image to a writable CD. Detailed instructions are available here for many operating systems: https://help.ubuntu.com/community/BurningIsoHowto

James: /* Verification with AppStudio */

2014-02-04T01:26:47Z

Verification with AppStudio

← Older revision		Revision as of 01:26, 4 February 2014
Line 388:		Line 388:
	* Set the username to the name of your ftp user.		* Set the username to the name of your ftp user.
	* Set the password to the password of your ftp user.		* Set the password to the password of your ftp user.
			* Click OK.

	[[File:Screenshot_2014-02-03_20.17.14.png]]		[[File:Screenshot_2014-02-03_20.17.14.png]]

	Now, when you deploy your application, you should be able to access it at: http://[servername]/[projectname]/		Now, when you deploy your application, you should be able to access it at: http://[servername]/[projectname]/

James: /* Uploading & Verification */

2014-02-04T01:25:01Z

Uploading & Verification

← Older revision		Revision as of 01:25, 4 February 2014
Line 376:		Line 376:

	It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked. Also, if the template files already exist in the upload, they will not be replaced by a link.		It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked. Also, if the template files already exist in the upload, they will not be replaced by a link.

			=== Verification with AppStudio ===

			You cannot verify the complete functionality of the server with AppStudio. You can, however, test he FTP and HTTP components of the server by configuring AppStudio to upload to your server directly:

			* Go into AppStudio's Preferences:
			** Windows: This will be in the Tools menu.
			** Mac OS: This will be in the AppStudio menu.
			* Change the Deployment Location to "Deploy to server listed below". You will only be able to perform this step if you have a registered copy.
			* Set the server to the hostname or IP address of the server you've just configured
			* Set the username to the name of your ftp user.
			* Set the password to the password of your ftp user.

			[[File:Screenshot_2014-02-03_20.17.14.png]]

			Now, when you deploy your application, you should be able to access it at: http://[servername]/[projectname]/

James: /* Verification */

2014-01-29T23:26:54Z

Verification

← Older revision		Revision as of 23:26, 29 January 2014
Line 375:		Line 375:
	If the system is working properly, a symbolic link to the template should have appeared in your project's folder after uploadng. Also, the file uploaded to NSB_UPLOAD_COMPLETE should have been removed.		If the system is working properly, a symbolic link to the template should have appeared in your project's folder after uploadng. Also, the file uploaded to NSB_UPLOAD_COMPLETE should have been removed.

	It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked.		It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked. Also, if the template files already exist in the upload, they will not be replaced by a link.

James: /* Configuring incron */

2014-01-28T08:54:33Z

Configuring incron

← Older revision		Revision as of 08:54, 28 January 2014
Line 316:		Line 316:

	if grep --quiet '<meta name="generator" content="NSB/AppStudio 3.*" />' /srv/ftp/home/$1/index.html; then		if grep --quiet '<meta name="generator" content="NSB/AppStudio 3.*" />' /srv/ftp/home/$1/index.html; then
	ln -s /srv/ftp/templates/3.3.x/* /srv/ftp/home/$1		ln -s /srv/ftp/templates/3.2.x/* /srv/ftp/home/$1
	fi		fi
	# add elif lines for more templates		# add elif lines for more templates

James: /* Copying "nsb" to the Template Folder */

2014-01-28T08:54:17Z

Copying "nsb" to the Template Folder

← Older revision		Revision as of 08:54, 28 January 2014
Line 299:		Line 299:

	<pre>		<pre>
	sudo cp -R ~/nsb /srv/ftp/templates/3.3.x/		sudo cp -R ~/nsb /srv/ftp/templates/3.2.x/
	</pre>		</pre>

James: /* Creating the proper folder structure */

2014-01-28T08:53:57Z

Creating the proper folder structure

← Older revision		Revision as of 08:53, 28 January 2014
Line 263:		Line 263:

	<pre>		<pre>
	sudo mkdir -p /srv/ftp/templates/3.3.x		sudo mkdir -p /srv/ftp/templates/3.2.x
	</pre>		</pre>

Ghenne at 11:18, 26 January 2014

2014-01-26T11:18:25Z

← Older revision		Revision as of 11:18, 26 January 2014
Line 254:		Line 254:

	<pre>		<pre>
	sudo mkdir -p /srv/ftp/~~AS_UPLOAD_COMPLETED~~		sudo mkdir -p /srv/ftp/NSB_UPLOAD_COMPLETED
	sudo mkdir -p /srv/ftp/templates		sudo mkdir -p /srv/ftp/templates
	sudo touch /srv/ftp/~~AS_UPLOAD_COMPLETED~~/.locked		sudo touch /srv/ftp/NSB_UPLOAD_COMPLETED/.locked
	sudo chown ftpuser:ftpuser /srv/ftp/~~AS_UPLOAD_COMPLETED~~		sudo chown ftpuser:ftpuser /srv/ftp/NSB_UPLOAD_COMPLETED
	</pre>		</pre>

Line 320:		Line 320:
	# add elif lines for more templates		# add elif lines for more templates

	rm /srv/ftp/~~AS_UPLOAD_COMPLETED~~/$1		rm /srv/ftp/NSB_UPLOAD_COMPLETED/$1
	</pre>		</pre>

Line 352:		Line 352:

	<pre>		<pre>
	/srv/ftp/~~AS_UPLOAD_COMPLETED~~ IN_CLOSE_WRITE /bin/bash /srv/ftp/templates/link.sh $# > /dev/null 2>&1		/srv/ftp/NSB_UPLOAD_COMPLETED IN_CLOSE_WRITE /bin/bash /srv/ftp/templates/link.sh $# > /dev/null 2>&1
	</pre>		</pre>

	Save the content with Ctrl-O. Incron should now be configured. You can verify this by creating a folder in /srv/ftp/home and then creating a file in /srv/ftp/~~AS_UPLOAD_COMPLETED~~ that shares the folder's name. The file you created should be removed and the folder should contain a link to your template.		Save the content with Ctrl-O. Incron should now be configured. You can verify this by creating a folder in /srv/ftp/home and then creating a file in /srv/ftp/NSB_UPLOAD_COMPLETED that shares the folder's name. The file you created should be removed and the folder should contain a link to your template.

	== Uploading & Verification ==		== Uploading & Verification ==
Line 367:		Line 367:
	# Choose a unique prefix for the folder based on the user's registration.		# Choose a unique prefix for the folder based on the user's registration.
	# Connect via FTP and upload the prefixed project folder into the ftp home folder.		# Connect via FTP and upload the prefixed project folder into the ftp home folder.
	# Change folders to ../~~AS_UPLOAD_COMPLETED~~ and drop a file in that folder that matches the name of the folder you just uploaded.		# Change folders to ../NSB_UPLOAD_COMPLETED and drop a file in that folder that matches the name of the folder you just uploaded.

	You can follow these steps manually to test the system.		You can follow these steps manually to test the system.
Line 373:		Line 373:
	=== Verification ===		=== Verification ===

	If the system is working properly, a symbolic link to the template should have appeared in your project's folder after uploadng. Also, the file uploaded to ~~AS_UPLOAD_COMPLETE~~ should have been removed.		If the system is working properly, a symbolic link to the template should have appeared in your project's folder after uploadng. Also, the file uploaded to NSB_UPLOAD_COMPLETE should have been removed.

	It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked.		It's important to note, that if the uploaded project does not contain "index.html" or the included "index.html" file does not contain a proper generator string (e.g. <code><meta name="generator" content="NSB/AppStudio 3</code>...) the template files will not be linked.

Ghenne: /* Uploading the "as" Folder */

2014-01-26T11:16:08Z

Uploading the "as" Folder

← Older revision		Revision as of 11:16, 26 January 2014
Line 266:		Line 266:
	</pre>		</pre>

	=== Uploading the "as" Folder ===		=== Uploading the "nsb" Folder ===

	First, you will need to locate the "as" folder, and upload it to your home folder. The directions vary by operating system.		First, you will need to locate the "nsb" folder, and upload it to your home folder. The directions vary by operating system.

	==== Windows ====		==== Windows ====

	* Navigate using Windows Explorer to "C:\Program Files (x86)\NSB AppStudio\". On older systems, the folder may be "Program Files" without the "(x86)".		* Navigate using Windows Explorer to "C:\Program Files (x86)\NSB AppStudio\". On older systems, the folder may be "Program Files" without the "(x86)".
	* Copy the "as" folder to your desktop.		* Copy the "nsb" folder to your desktop.
	* Download and install an SFTP client, such as WinSCP: http://winscp.net/eng/index.php		* Download and install an SFTP client, such as WinSCP: http://winscp.net/eng/index.php
	* Connect to your server using the following instructions as a guide: http://winscp.net/eng/docs/guide_connect		* Connect to your server using the following instructions as a guide: http://winscp.net/eng/docs/guide_connect
	* WinSCP should default ~~it's~~ remote location to your home folder on the server. Upload the "as" folder on your desktop to your home folder using the following instructions as a guide: http://winscp.net/eng/docs/guide_upload		* WinSCP should default its remote location to your home folder on the server. Upload the "nsb" folder on your desktop to your home folder using the following instructions as a guide: http://winscp.net/eng/docs/guide_upload

	==== Mac OS ====		==== Mac OS ====
Line 284:		Line 284:
	* Choose "Show Package Contents"		* Choose "Show Package Contents"
	* In the Finder window that appears, navigate to "Contents/Resources".		* In the Finder window that appears, navigate to "Contents/Resources".
	* Copy the "as" folder to your desktop.		* Copy the "nsb" folder to your desktop.
	* Open the Terminal application in Mac OS, and type the following:		* Open the Terminal application in Mac OS, and type the following:

	<pre>		<pre>
	cd ~/Desktop		cd ~/Desktop
	scp -r as user@server01:.		scp -r nsb user@server01:.
	</pre>		</pre>

	Be sure to replace "user" and "server01" with your username and server's hostname.		Be sure to replace "user" and "server01" with your username and server's hostname.

	==== Copying "as" to the Template Folder ====		==== Copying "nsb" to the Template Folder ====

	Finally, copy the "as" folder to the template folder you created. While logged into your server, type the following:		Finally, copy the "nsb" folder to the template folder you created. While logged into your server, type the following:

	<pre>		<pre>
	sudo cp -R ~/as /srv/ftp/templates/3.3.x/		sudo cp -R ~/nsb /srv/ftp/templates/3.3.x/
	</pre>		</pre>