Configuring the development environment
Working with NTCP and clients demands a fairly complicated development
environment. This page explains two different distributions, and two
different deployement environments, with emphasis on the details
required to get it going.
Requirements
To start with, you'll need a development machine. It's quite possible
to do all of your work on one machine if necessary. The normal
configuration includes what's known as 'the NEES-POP' machine, a Linux
box running the NEESGrid software. However, you can install NTCP by
itself for development, and that will be covered in this document.
There are separate instruction pages for the two different
configurations, just to avoid any confusion.
I will cover what I think are the two most common configurations.
- Local development on your own machine (laptop or desktop), and
NTCP running on the NEES-POP:
If this matches your setup, follow
this link to read on.
- All development on your own machine. Actually, this case is more
general; go this way if you're not using the NEES-POP distribution:
If this is how you will work, please proceed
to this page.