MANDATORY PRE-REQUISITE STEPS (NEEDED BY ALL DEMOS BELOW)

Perform step 1 or 2 below according to your experience and apply the overrides to your StackScript as described below for your desired demo type before you click "Create Linode"

  1. If you are a beginner, follow here
  2. If you are an expert, follow here

QUICK DEMO OVERRIDE EXAMPLES

Once you have performed the mandatory steps above you can action specific demos by overriding the mentioned settings in the StackScript before you deploy it. By overriding different settings as described below, you will deploy different application types using the same StackScript.

Demo 1 (StackScript overrides for a virgin installation of the Joomla CMS)

set "The number (1, 2 or 3) of the template you are using" to "1"  
set "WEBSITE DISPLAY NAME" to "My Joomla Demo"  
set "APPLICATION" to "joomla"  
set "JOOMLA VERSION" and set it to the latest version of Joomla for example, "5.1.2"  
set "BUILD ARCHIVE CHOICE" to "virgin"  
set "BASELINE DB REPOSITORY" to "VIRGIN"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "JOOMLA:5.1.2"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="1"
export WEBSITE_DISPLAY_NAME="My Joomla Demo"
export APPLICATION="joomla"
export JOOMLA_VERSION="5.1.2"
export BUILD ARCHIVE CHOICE="virgin"
export BASELINE DB REPOSITORY="VIRGIN"
export APPLICATION BASELINE SOURCECODE REPOSITORY="JOOMLA:5.1.2"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@156.23.43.21
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Joomla installation in my case:

https://www.nuocial.uk

and complete the installation of Joomla. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

IMPORTANT:

You will be prompted to remove the file beginning /var/www/html/installation/_J.... The Agile Deployment Toolkit will do that for your automatically all you need to do when prompted to remove the /var/www/html/installation/_J.... file is to click through a second time (at the bottom of the page prompting you to action) and you will be able to progress without doing anything.

Demo 2 (StackScript overrides for a virgin installation of the Wordpress CMS)

set "The number (1, 2 or 3) of the template you are using" to "1"  
set "WEBSITE DISPLAY NAME" to "My Wordpress Demo"  
set "APPLICATION" to "wordpress"  
set "BUILD ARCHIVE CHOICE" to "virgin"  
set "BASELINE DB REPOSITORY" to "VIRGIN"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "WORDPRESS"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="1"
export WEBSITE_DISPLAY_NAME="My Wordpress Demo"
export APPLICATION="wordpress"
export BUILD ARCHIVE CHOICE="virgin"
export BASELINE DB REPOSITORY="VIRGIN"
export APPLICATION BASELINE SOURCECODE REPOSITORY="WORDPRESS"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@121.34.32.65
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Wordpress installation in my case:

https://www.nuocial.uk

and complete the installation of Wordpress. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

Demo 3 (StackScript overrides for a virgin installation of Drupal, Drupal CMS or Drupal Opensocial)

NOTE:

If you see an error message:

At any point during the installation of a drupal application its very likely becsause the cache is inconsistent. Apart from being unsightly its not a problem or even really an error all you have to do is run 

${BUILD_HOME}/helperscripts/TruncateDrupalCache.sh.

This will then refresh/rebuild the drupal caching system and the website should then display properly. If anyone knows a cleaner way of achieving this without the error message appearing I would be interested to know because I am not a drupal or any other CMS expert.

DRUPAL (10.0.10) 

set "The number (1, 2 or 3) of the template you are using" to "1"  
set "WEBSITE DISPLAY NAME" to "My Drupal Demo" 
set "APPLICATION" to "drupal"   
set "DRUPAL VERSION" set it to the latest version of drupal for example, "10.0.10" 
set "BUILD ARCHIVE CHOICE" to "virgin"   
set "BASELINE DB REPOSITORY" to "VIRGIN"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "DRUPAL:10.0.10"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="1"
export WEBSITE_DISPLAY_NAME="My Drupal Demo"
export APPLICATION="drupal"
export DRUPAL_VERSION="10.0.10""
export BUILD ARCHIVE CHOICE="virgin"
export BASELINE DB REPOSITORY="VIRGIN"
export APPLICATION BASELINE SOURCECODE REPOSITORY="DRUPAL:10.0.10"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@121.34.32.65
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Wordpress installation in my case:

https://www.nuocial.uk

and complete the installation of Wordpress. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

NOTE: If you get an error message "The website encountered an unexpected error. Try again later" from Drupal CMS once it is installed you need to "clear all caches" which you can do by running

${BUILD_HOME}/helperscripts/TruncateDrupalCache.sh

on your new build machine.

OPENSOCIAL

You can install OPENSOCIAL by making the following alterations to the above DRUPAL (10.0.10) install method

set "The Display name for your website e.g. My Demo Website" to "My Opensocial Demo"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "DRUPAL:social"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@102.12.32.12
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Wordpress installation in my case:

https://www.nuocial.uk

and complete the installation of Opensocial. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

NOTE: If you get an error message "The website encountered an unexpected error. Try again later" from Drupal CMS once it is installed you need to "clear all caches" which you can do by running

${BUILD_HOME}/helperscripts/TruncateDrupalCache.sh

on your new build machine.

DRUPAL CMS

You can install DRUPAL CMS by making the following alterations to the above DRUPAL (10.0.10) install method

You can install by making the modification to the steps above:

set "The Display name for your website e.g. My Demo Website" to "My Druapl CMS Demo"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "DRUPAL:cms"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@102.12.32.12
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Wordpress installation in my case:

https://www.nuocial.uk

and complete the installation of Drupal. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

NOTE: If you get an error message "The website encountered an unexpected error. Try again later" from Drupal CMS once it is installed you need to "clear all caches" which you can do by running

${BUILD_HOME}/helperscripts/TruncateDrupalCache.sh

on your new build machine.

Demo 4 (StackScript overrides for a virgin installation of the Moodle CMS)

set "The number (1, 2 or 3) of the template you are using" to "1"  
set "WEBSITE DISPLAY NAME" to "My Moodle Demo"  
set "APPLICATION" to "moodle"  
set "BUILD ARCHIVE CHOICE" to "virgin"  
set "BASELINE DB REPOSITORY" to "VIRGIN"  
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "MOODLE"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="1"
export WEBSITE_DISPLAY_NAME="My Moodle Demo"
export APPLICATION="moodle"
export BUILD ARCHIVE CHOICE="virgin"
export BASELINE DB REPOSITORY="VIRGIN"
export APPLICATION BASELINE SOURCECODE REPOSITORY="MOODLE"

To find what to set your application credentials to ssh onto your new build machine sudo to root and cat the application_credentials.dat file that the build generated as shown below

ssh -p <build-machine-port> <username>@<build-machine-ip>
sudo su
     <password>
/bin/cat /home/<username>/adt-build-machine-scripts/runtimedata/linode/<build-identifier>/credentials/application_credentials.dat

which in my case looks like:

ssh -p 1035 agile-deployer@78.98.32.19
/bin/cat /home/agile-deployer/adt-build-machine-scripts/runtimedata/linode/test-build/credentials/application_credentials.dat

Go to the URL of your virgin Moodle installation in my case:

https://www.nuocial.uk

and complete the installation of Wordpress. When you are putting the credentials you got from application_credentials.dat from your build machine the installation process should look similar to:

Demo 5 (StackScript overrides for a virgin installation of the Joomla CMS from a baselined repository)

This is just a sample virgin joomla install there's no sample data or anything it just shows you how you could baseline a virgin joomla installation for maximum ease when making repeated virgin CMS deployments. The advantage to creating a baseline of a virgin installation of a CMS is that you don't have to enter any parameters into the application GUI because the system deals with it all for you and so you can make faster deployments once you have a baseline to build from. The disadvantage is that you have to update the installed CMS from the administrator backend to the latest version because the baseline you made some weeks/months ago will be several releases back from current.

  1. Once the application is installed, the username is "webmaster" and the password is "mnbcxz098321QQZZ"
set "The number (1, 2 or 3) of the template you are using" to "2"  
set "The Display name for your website e.g. My Demo Website" to "My Vanilla Joomla Installation"  
set "APPLICATION" to "joomla"  
set "BASELINE DB REPOSITORY" to "joomla5.2.5-db-baseline" 
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "joomla5.2.5-webroot-sourcecode-baseline"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="2"
export WEBSITE_DISPLAY_NAME="My Vanilla Joomla Installation"
export APPLICATION="joomla"
export BASELINE DB REPOSITORY="joomla5.2.5-db-baseline"
export APPLICATION BASELINE SOURCECODE REPOSITORY="joomla5.2.5-webroot-sourcecode-baseline"

Wait for the application install to have been completed and available at:

 https://<dns-url>

Demo 6 (StackScript overrides for a virgin installation of the Wordpress CMS from a baselined repository)

This is a sample virgin wordpress installation from baselined repositories.

  1. Once the application is installed, the username is "webmaster" and the password is "mnbcxz098321QQZZ"
set "The number (1, 2 or 3) of the template you are using" to "2"  
set "The Display name for your website e.g. My Demo Website" to "My Vanilla Wordpress Installation"  
set "APPLICATION" to "wordpress"  
set "BASELINE DB REPOSITORY" to "wordpress6.8.2-db-baseline" 
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "wordpress6.8.2-webroot-sourcecode-baseline"

Wait for the application install to have been completed and available at:

 https://<dns-url>

Demo 7 (StackScript overrides for a virgin installation of the Drupal CMS from a baselined repository)

This is a sample virgin drupal installation from baselined repositories.

  1. Once the application is installed, the username is "webmaster" and the password is "mnbcxz098321QQQZZZ"
set "The number (1, 2 or 3) of the template you are using" to "2"  
set "The Display name for your website e.g. My Demo Website" to "My Vanilla Drupal Installation"  
set "APPLICATION" to "drupal"  
set "BASELINE DB REPOSITORY" to "drupal11.1.7-db-baseline" 
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "drupal11.1.7-webroot-sourcecode-baseline"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="2"
export WEBSITE_DISPLAY_NAME="My Vanilla Drupal Installation"
export APPLICATION="drupal"
export BASELINE DB REPOSITORY="drupal11.1.7-db-baseline"
export APPLICATION BASELINE SOURCECODE REPOSITORY="drupal11.1.7-webroot-sourcecode-baseline"

Wait for the application install to have been completed and available at:

 https://<dns-url>

NOTE: If you get an error message "The website encountered an unexpected error. Try again later" from Drupal CMS once it is installed you need to "clear all caches" which you can do by running

${BUILD_HOME}/helperscripts/TruncateDrupalCache.sh

on your new build machine.

Demo 8 (StackScript overrides for a virgin installation of the Moodle CMS from a baselined repository)

This is a sample virgin moodle installation from baselined repositories.

  1. Once the application is installed, the username is "webmaster" and the password is "mnbcxz098321QQQZZZ$$"
set "The number (1, 2 or 3) of the template you are using" to "2"  
set "The Display name for your website e.g. My Demo Website" to "My Vanilla Moodle Installation"  
set "APPLICATION" to "moodle"  
set "BASELINE DB REPOSITORY" to "moodle5.0-db-baseline" 
set "APPLICATION BASELINE SOURCECODE REPOSITORY" to "moodle5.0-webroot-sourcecode-baseline"

If you are using the cloud-init method raher than StackScript these you should set

export SELECTED_TEMPLATE="2"
export WEBSITE_DISPLAY_NAME="My Vanilla Moodle Installation"
export APPLICATION="moodle"
export BASELINE DB REPOSITORY="moodle5.0-db-baseline"
export APPLICATION BASELINE SOURCECODE REPOSITORY="moodle5.0-webroot-sourcecode-baseline"

Wait for the application install to have been completed and available at:

 https://<dns-url>