GAE Variant Skip this step
Let us assume at this point that MyApp is complete and working.
Theoretically, it could be hosted via an intranet or even globally by making your internal server running this code accessible to the internet. This may not be ideal for the following reasons:
Limited to a single machine serving
There is no built in data redundancy like that provided with the Node.js hosting sites
To move MyApp to the
Node Jitsu Site.
the following steps are required. It will be necessary to adjust this if you choose a hosting different site.
If you do not yet have one get a Node Jitsu Account
Update def-app.htm to reflect the default application you wish to use if none is specified.
Set CWD to in theX:\tri-devp\war folder.
Follow the instructions at
Node Jitsu CLI which uses the Jitsu command to
upload the website. When asked your startup code is js/tri-server.js This by default will use port 80 and
will use def-app.htm as the first page which will redirct to the default application.
MyApp
At this point we are making sure the plumbing is working. Nothing in MyApp should be affected by the move to the NodeJS Site
including the Datastore NodeJS because it is part of the upload.
If MyApp is intended to be the default app then access it with a browser with URL http://tri-demo.nodejitsu.com/
If MyApp is not intended to be the default app then access it with a browser with URL http://tri-demo.nodejitsu.com/apps/MyApp.htm
If the demo apps are removed from the x:\tri-devp\apps folder then their use will cause Error 404 to be displayed on the browser.
If they are not removed the signon page for each app will still be presented and you will be able to login.
Google Analytics
Exercise the MyApp on the NodeJS Site.
Within 30 minutes logon to your Google Analytics Account.
Navigate to your tracker code reporting page.
Use the Real-Time left side tab to check out the expected recording of the analytics events.
Overnight this will be recorded in the historic records which are viewed under the Audience and Behavoir tabs.