Guide to running dcServer on your local machine

It is recommended that web developers using dcServer run a local version of the server for development and testing. There are tools provided for syncing your changes with the production server, but this guide is only about quickly getting a local server ready as one might in preparation for development of new website sites.

Preparation

Your System:

Linux: perfect. The instructions are based on Ubuntu, but should work for you
MacOS: should work but may need adjustments, these instructions are not tested on Mac
Windows: If you are coding on Windows you'll need to use WSL and note that these instructions are not tested on Windows.

Installations:

Install Java 11, we recommend Amazon Corretto
higher versions of Java should work but are not tested, use java --version to check your version
be sure the JAVA_HOME environment variable is set (for example, in .bashrc ), on Ubuntu it would look something like this export JAVA_HOME=/usr/lib/jvm
Install a decent text editor if you don't already have one. I like Atom.
Install Git and Git LFS if you want to track your website development in Git. Using Git is especially advisable if planning to develop on more than one computer, such as with teammates.

For more advanced work you may also want a Java IDE, however, for most basic website coding you do not need to code in Java. Editing website files in a text editor should be quite sufficient for getting started.

Get dcServer

Download the latest release:
https://cdn.designcraftadvertising.com/prod-2/dcc/files/releases/dcServer-2023-01-29.tar.gz

If using Git to track your development, create a repository and initialize Git LFS first. Otherwise simply create your project folder. For this guide let's refer to the folder as dcserver-one , for example mkdir dcserver-one .

Extract the release into the project folder, for example:

tar -xzvf dcServer-2023-01-29.tar.gz -C dcserver-one/

Make sure the path (after -C) to the project folder is reachable (relative to current path or absolute path).

$ ls -la

drwxrwxr-x 4 gadreel gadreel 4096 Apr 23 08:15 .
drwxrwxr-x 4 gadreel gadreel 4096 Apr 23 08:13 ..
-rwxr-xr-x 1 gadreel gadreel  822 Oct 13  2020 foreground.sh
-rwxrwxr-x 1 gadreel gadreel  896 Mar  4 07:35 ignite.sh
drwxrwxr-x 3 gadreel gadreel 4096 Apr 23 08:12 lib
-rw-rw-r-- 1 gadreel gadreel  365 Apr 23 09:21 matrix.xml
drwxr-xr-x 3 gadreel gadreel 4096 Sep 21  2019 packages
-rwxr-xr-x 1 gadreel gadreel 1280 Oct 16  2020 server.sh

Configure a Deployment

Each website must live within a deployment and most deployments consist of one production server, though there could be more. Some servers (deployments) may have many websites, others might have only one website.

For the quick start lets assume one website on a server (deployment), though you may add more later.

You'll need a short alphanumeric (dashes allowed) alias for your deployment. In our examples we'll use kipo but you may use your own alias anywhere you see kipo .

The matrix.xml files lists your deployments. Please edit that file and set your alias in the Alias attribute.

<Matrix>
  <DeveloperNodes>
      <Node Id="00100" Note="Developer One" IsProduction="False">
          <SSH KeyFile="~/path-to-keys/my-servers.pem" PublicKeyFile="~/path-to-keys/my-servers.pub" />
      </Node>
  </DeveloperNodes>

    <Deployment Alias="kipo" Title="quick start server" Template="dca/standard">
        <Node Id="99999" Note="Demo Server" />
    </Deployment>
</Matrix>

Now, to add a deployment run the ignite.sh shell script.

$ ./ignite.sh

dcServer starting
Adding Ignite deployment, this may take a couple of minutes.
new encryptor key: 3c2bc80db5bb61753efb065ca9dc22d9cb1b1adc
new ignite key: 4dd5fc4da50981dc51360be3398acac6213a0e74
new tenant security key: 6a3452bb7a40b0240d444eca2be2384e3a84bb0b
20220423T141233518Z 000000000000000 M03 |OpId|00001-20220423T141231276Z-000000000000000| New operation context
Start local hub loader work
20220423T141233569Z 000000000000000 M03 Loading hub resources
20220423T141233820Z 000000000000000 M03 Hub resources loaded
20220423T141233985Z 000000000000000 B   |Origin|hub:|Op|Start|
20220423T141233985Z 000000000000000 M03 Hub deployment: ignite
20220423T141233986Z 000000000000000 M03 Hub role: ignite
20220423T141233986Z 000000000000000 M03 Hub id: 00001
20220423T141233987Z 000000000000000 M03 Is hub production: false
20220423T141233988Z 000000000000000 M03 Java version: 11.0.4
20220423T141233989Z 000000000000000 M03 Java vendor: Amazon.com Inc.
20220423T141233989Z 000000000000000 M03 Java vm: OpenJDK 64-Bit Server VM
20220423T141234040Z 000000000000000 M03 /dev/epoll: yes
20220423T141234256Z 000000000000000 M03 OpenSSL: yes (BoringSSL, 269488255))
20220423T141234269Z 000000000000000 M03 |OpId|00001-20220423T141231276Z-000000000000001| New operation context
20220423T141234272Z 000000000000000 M03 |OpId|00001-20220423T141231276Z-000000000000002| New operation context
20220423T141234295Z 000000000000000 M03 |OpId|00001-20220423T141231276Z-000000000000003| New operation context
20220423T141234297Z 000000000000000 M03 Hub entered Booted state
20220423T141234297Z 000000000000000 B   |Origin|hub:|Op|Run|
20220423T141234298Z 000000000000000 M03 Hub entered Running state
20220423T141236299Z 000000000000000 M03 |OpId|00001-20220423T141231276Z-000000000000004| New operation context
20220423T141236305Z 000000000000004 M03 |SessId|00001_1rrhrpvi7mc2kbt464e8fonf9k| Session registered

-----------------------------------------------
   dcIGNITE main menu
-----------------------------------------------
0)   Exit
1)   Add Deployment
20)  Hub Utilities

Now select option 1.

-----------------------------------------------
   Deployment Initialization
-----------------------------------------------

You will need a matrix.xml before you can add a deployment.
In the matrix you need to add the Deployment entry for the new deployment.
Also in matrix you will want to add DeveloperNodes and DeploymentTemplates.

Are you sure you want to continue (y/n)?

Enter “y”

Choose a deployment to initialize:

1) quick start server - kipo

Enter the number:

Enter “1”

Initializing quick start server
Enter deployment time zone in full tz database format (e.g. America/Chicago):

Enter a timezone or enter for default.

This will be your keyring password, please keep with your files: XNNNNNNNNNNX
Typically you do not need this password, but for recovery it could be useful.
new encryptor key: NNNNNNNNNN
new ignite key: NNNNNNNNNN
Common keys built
new node sign key: NNNNNNNNNN
new node sign key: NNNNNNNNNN
Nodes initialized
new tenant security key: NNNNNNNNNN
Deployment initialization exiting.

-----------------------------------------------
   dcIGNITE main menu
-----------------------------------------------
0)   Exit
1)   Add Deployment
20)  Hub Utilities

Keep the password generated above in a safe place (the one indicated by 'XNNNNNNNNNNX').

And enter “0”

If you list your directory again, there will be two new folders:

drwxrwxr-x 6 gadreel gadreel 4096 Apr 23 10:21 deploy-ignite
drwxrwxr-x 6 gadreel gadreel 4096 Apr 23 10:21 deploy-kipo

The deploy-ignite tracks a common set of signing keys trusted by all your other deployments. This deployment isn't used for anything else, do not try to run it.

The deploy-kipo (or whatever alias you selected) folder has your new basic deployment in it. The next step is to add a website.

Initialize the Node's Database

$ ./foreground.sh kipo 00100 init-node
dcServer starting
20220424T120424561Z 000000000000000 M03 |OpId|00100-20220424T120424258Z-000000000000000| New operation context
Start local hub loader work
20220424T120424866Z 000000000000000 M03 Loading hub resources
20220424T120425248Z 000000000000000 M03 Hub resources loaded
20220424T120425462Z 000000000000000 B   |Origin|hub:|Op|Start|
20220424T120425463Z 000000000000000 M03 Hub deployment: kipo
20220424T120425464Z 000000000000000 M03 Hub role: init-node
20220424T120425465Z 000000000000000 M03 Hub id: 00100
20220424T120425466Z 000000000000000 M03 Is hub production: false
20220424T120425466Z 000000000000000 M03 Java version: 11.0.4
20220424T120425467Z 000000000000000 M03 Java vendor: Amazon.com Inc.
20220424T120425468Z 000000000000000 M03 Java vm: OpenJDK 64-Bit Server VM
20220424T120425516Z 000000000000000 M03 /dev/epoll: yes
20220424T120425754Z 000000000000000 M03 OpenSSL: yes (BoringSSL, 269488255))
20220424T120425768Z 000000000000000 M03 |OpId|00100-20220424T120424258Z-000000000000001| New operation context
20220424T120425772Z 000000000000000 M03 |OpId|00100-20220424T120424258Z-000000000000002| New operation context
20220424T120425797Z 000000000000000 M03 |OpId|00100-20220424T120424258Z-000000000000003| New operation context
20220424T120425799Z 000000000000000 M03 Hub entered Booted state
20220424T120425799Z 000000000000000 B   |Origin|hub:|Op|Run|
20220424T120425800Z 000000000000000 M03 Hub entered Running state
20220424T120425800Z 000000000000000 M03 |OpId|00100-20220424T120424258Z-000000000000004| New operation context
20220424T120425809Z 000000000000004 M03 |SessId|00100_u7l140a07p2rnu05beq7frjbgj| Session registered
Password:

[enter plain *]

-----------------------------------------------
   Node Initialization
-----------------------------------------------

You could lose your node setup (database) by doing this command.
Are you sure you want to continue (y/n)?

Initialize Root Tenant

Global Root Password (required):

[enter a new password]

Root User Email (required):

[enter your email]

Node:

00100

20220424T120446279Z 000000000000004 M03 dcDatabase Started
Root added
20220424T120446419Z 000000000000004 M03 dcDatabase Stopped
Database configured, root tenant added.
20220424T120446420Z 000000000000004 M03 Ending session: 00100_u7l140a07p2rnu05beq7frjbgj
20220424T120446420Z 000000000000004 M03 Stopping Application Server
20220424T120446426Z 000000000000004 M03 |OpId|00100-20220424T120424258Z-000000000000005| New operation context
20220424T120446428Z 000000000000005 M03 Hub entered Stopping state
20220424T120446428Z 000000000000005 M03 Hub entered Stopping state
20220424T120446429Z 000000000000005 B   |Origin|hub:|Op|Stop|
20220424T120446429Z 000000000000005 M03 Stopping hub
20220424T120446434Z 000000000000005 M03 Hub stopped
20220424T120446435Z 000000000000005 M03 Hub entered Stopped state
20220424T120446436Z 000000000000004 M03 Application hub shutdown started
20220424T120446439Z 000000000000004 M03 Application hub shutdown completed

Add a Website (aka tenant)

Before doing this step be sure there are no processes using ports 8080 and 8443 on your computer. If you are not sure, run this and look for an error message.

$ ./foreground.sh kipo 00100
dcServer starting
20220424T120704248Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000000| New operation context
Start local hub loader work
20220424T120704545Z 000000000000000 M03 Loading hub resources
20220424T120704942Z 000000000000000 M03 Hub resources loaded
20220424T120705181Z 000000000000000 B   |Origin|hub:|Op|Start|
20220424T120705182Z 000000000000000 M03 Hub deployment: kipo
20220424T120705183Z 000000000000000 M03 Hub role: server
20220424T120705184Z 000000000000000 M03 Hub id: 00100
20220424T120705184Z 000000000000000 M03 Is hub production: false
20220424T120705185Z 000000000000000 M03 Java version: 11.0.4
20220424T120705186Z 000000000000000 M03 Java vendor: Amazon.com Inc.
20220424T120705186Z 000000000000000 M03 Java vm: OpenJDK 64-Bit Server VM
20220424T120705242Z 000000000000000 M03 /dev/epoll: yes
20220424T120705482Z 000000000000000 M03 OpenSSL: yes (BoringSSL, 269488255))
20220424T120705509Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000001| New operation context
20220424T120705514Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000002| New operation context
20220424T120705645Z 000000000000000 M03 dcDatabase Started
20220424T120705659Z 000000000000000 M03 dcDatabase Service Started
20220424T120705665Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000003| New operation context
20220424T120705671Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000004| New operation context
20220424T120705674Z 000000000000000 M03 Hub entered Booted state
20220424T120705675Z 000000000000000 B   |Origin|hub:|Op|Run|
20220424T120705676Z 000000000000000 M03 Hub entered Running state
20220424T120705815Z 000000000000000 M03 Web Server listening - now listening for HTTP on TCP port 8443
20220424T120705817Z 000000000000000 M03 Web Server listening - now listening for HTTP on TCP port 8080
20220424T120705817Z 000000000000000 M03 |OpId|00100-20220424T120703951Z-000000000000005| New operation context
20220424T120705826Z 000000000000005 M03 |SessId|00100_m98bcj8uu4eq50gcobino4gs70| Session registered
Password:

your password

-----------------------------------------------
   Hub General Utils
-----------------------------------------------
0)   Exit
1)   dcDatabase Utils
2)   Local Utilities
3)   Crypto Utilities
100) dcScript GUI Debugger
101) dcScript Run Script

-----------------------------------------------
   Hub 00100 DB Utility Menu
-----------------------------------------------
0)  Exit
1)  Database Dump
2)  Create Database
3)  Initialize Root Tenant (create db if not present)
4)  Backup Database
5)  Database Backup Info
6)  Restore Database
7)  Compact Database - TODO
8)  Mess Database
9)  Re-index dcTables
10)  Add Tenant

Tenant Alias:

kipo

Tenant Name:

Kipo Website

Local Domain Name:
(domain used to run locally)

l-kipo.com

tenant-shared written
creating tenant keys - this can take some time, please wait
new tenant security key: 59774469d32c0f24f670f0401bb4da7e0be57252
tenant keys built
Add Tenant Messages:
 [

 ]

Add Tenant Response:
[empty]
tenant added to db, restart server to activate

-----------------------------------------------
   Hub 00100 DB Utility Menu
-----------------------------------------------
0)  Exit
1)  Database Dump
2)  Create Database
3)  Initialize Root Tenant (create db if not present)
4)  Backup Database
5)  Database Backup Info
6)  Restore Database
7)  Compact Database - TODO
8)  Mess Database
9)  Re-index dcTables
10)  Add Tenant

-----------------------------------------------
   Hub General Utils
-----------------------------------------------
0)   Exit
1)   dcDatabase Utils
2)   Local Utilities
3)   Crypto Utilities
100) dcScript GUI Debugger
101) dcScript Run Script

20220424T120739449Z 000000000000005 M03 Ending session: 00100_m98bcj8uu4eq50gcobino4gs70
20220424T120739450Z 000000000000005 M03 Stopping Application Server
20220424T120739461Z 000000000000005 M03 |OpId|00100-20220424T120703951Z-000000000000006| New operation context
20220424T120739463Z 000000000000006 M03 Hub entered Stopping state
20220424T120739465Z 000000000000006 M03 Web Server unbound
20220424T120739466Z 000000000000006 M03 Web Server unbound
20220424T120739466Z 000000000000006 M03 Hub entered Stopping state
20220424T120739466Z 000000000000006 B   |Origin|hub:|Op|Stop|
20220424T120739467Z 000000000000006 M03 Stopping hub
20220424T120739469Z 000000000000006 M03 dcDatabase Stopped
20220424T120741490Z 000000000000006 M03 Hub stopped
20220424T120741490Z 000000000000006 M03 Hub entered Stopped state
20220424T120741491Z 000000000000005 M03 Application hub shutdown started
20220424T120741496Z 000000000000005 M03 Application hub shutdown completed

Configure the Host Name

Edit the hosts file, in Ubuntu you could use:

sudo gedit /etc/hosts

Add new lines for the host (domain) name you used above. Likely you only need the IPv6 address, but just in case add both.

127.0.0.1   l-kipo.com
::1         l-kipo.com

Code the Website

create a www folder in folder deploy-kipo/tenants/kipo

create a home.html file in folder deploy-kipo/tenants/kipo/www

This is a static website so no special tags are available, just something simple like:

<html>
  <body>
    Hello World
  </body>
</html>

Test the Site

Run the web server:

$ ./foreground.sh kipo 00100
dcServer starting
20220424T120930152Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000000| New operation context
Start local hub loader work
20220424T120930495Z 000000000000000 M03 Loading hub resources
20220424T120930965Z 000000000000000 M03 Hub resources loaded
20220424T120931196Z 000000000000000 B   |Origin|hub:|Op|Start|
20220424T120931197Z 000000000000000 M03 Hub deployment: kipo
20220424T120931198Z 000000000000000 M03 Hub role: server
20220424T120931199Z 000000000000000 M03 Hub id: 00100
20220424T120931200Z 000000000000000 M03 Is hub production: false
20220424T120931201Z 000000000000000 M03 Java version: 11.0.4
20220424T120931201Z 000000000000000 M03 Java vendor: Amazon.com Inc.
20220424T120931202Z 000000000000000 M03 Java vm: OpenJDK 64-Bit Server VM
20220424T120931250Z 000000000000000 M03 /dev/epoll: yes
20220424T120931479Z 000000000000000 M03 OpenSSL: yes (BoringSSL, 269488255))
20220424T120931512Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000001| New operation context
20220424T120931515Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000002| New operation context
20220424T120931651Z 000000000000000 M03 dcDatabase Started
20220424T120931666Z 000000000000000 M03 dcDatabase Service Started
20220424T120931673Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000003| New operation context
20220424T120931679Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000004| New operation context
20220424T120931683Z 000000000000000 M03 Hub entered Booted state
20220424T120931683Z 000000000000000 B   |Origin|hub:|Op|Run|
20220424T120931684Z 000000000000000 M03 Hub entered Running state
20220424T120931868Z 000000000000000 M03 Web Server listening - now listening for HTTP on TCP port 8443
20220424T120931870Z 000000000000000 M03 Web Server listening - now listening for HTTP on TCP port 8080
20220424T120931870Z 000000000000000 M03 |OpId|00100-20220424T120929891Z-000000000000005| New operation context
20220424T120931877Z 000000000000005 M03 |SessId|00100_9m5652nn4t0u74bhk07at1mb4g| Session registered
Password:

look for any M01 in the column of M03, if any appear then an error occurred during the start of the server. If there are no errors shown then you should be fine. There is no need to login when testing the website.

Open the website in browser:

http://l-kipo.com:8080/

Second Development Computer

If you are using a git repo then it is easy to add other development computers, whether it is a second computer for you or for your teammate(s). Before you clone the repo add another developer node. Do not use the same node id on multiple developer systems or installs, even if you have a second install on the same computer.

Edit the matrix.xml and duplicate the Node element like so.

<Matrix>
  <DeveloperNodes>
      <Node Id="00100" Note="Developer One" IsProduction="False">
          <SSH KeyFile="~/path-to-keys/my-servers.pem" PublicKeyFile="~/path-to-keys/my-servers.pub" />
      </Node>
      <Node Id="00101" Note="Developer Two" IsProduction="False">
          <SSH KeyFile="~/path-to-keys/my-servers.pem" PublicKeyFile="~/path-to-keys/my-servers.pub" />
      </Node>
  </DeveloperNodes>

    <Deployment Alias="kipo" Title="quick start server" Template="dca/standard">
        <Node Id="99999" Note="Demo Server" />
    </Deployment>
</Matrix>

Create new signing keys for this new node. Run Ignite again.

$ ./ignite.sh
dcServer starting
20220430T134241553Z 000000000000000 M03 |OpId|00001-20220430T134241193Z-000000000000000| New operation context
Start local hub loader work
20220430T134241960Z 000000000000000 M03 Loading hub resources
20220430T134242413Z 000000000000000 M03 Hub resources loaded
20220430T134242703Z 000000000000000 B   |Origin|hub:|Op|Start|
20220430T134242704Z 000000000000000 M03 Hub deployment: ignite
20220430T134242704Z 000000000000000 M03 Hub role: ignite
20220430T134242705Z 000000000000000 M03 Hub id: 00001
20220430T134242706Z 000000000000000 M03 Is hub production: false
20220430T134242707Z 000000000000000 M03 Java version: 11.0.4
20220430T134242707Z 000000000000000 M03 Java vendor: Amazon.com Inc.
20220430T134242708Z 000000000000000 M03 Java vm: OpenJDK 64-Bit Server VM
20220430T134242769Z 000000000000000 M03 /dev/epoll: yes
20220430T134243025Z 000000000000000 M03 OpenSSL: yes (BoringSSL, 269488255))
20220430T134243040Z 000000000000000 M03 |OpId|00001-20220430T134241193Z-000000000000001| New operation context
20220430T134243045Z 000000000000000 M03 |OpId|00001-20220430T134241193Z-000000000000002| New operation context
20220430T134243078Z 000000000000000 M03 |OpId|00001-20220430T134241193Z-000000000000003| New operation context
20220430T134243080Z 000000000000000 M03 Hub entered Booted state
20220430T134243081Z 000000000000000 B   |Origin|hub:|Op|Run|
20220430T134243081Z 000000000000000 M03 Hub entered Running state
20220430T134245082Z 000000000000000 M03 |OpId|00001-20220430T134241193Z-000000000000004| New operation context
20220430T134245089Z 000000000000004 M03 |SessId|00001_j2fq7jvr9oguqc65mrgcuiaeul| Session registered

-----------------------------------------------
   dcIGNITE main menu
-----------------------------------------------
0)   Exit
1)   Add Deployment
20)  Hub Utilities

-----------------------------------------------
   Hub General Utils
-----------------------------------------------
0)   Exit
1)   dcDatabase Utils
2)   Local Utilities
3)   Crypto Utilities
100) dcScript GUI Debugger
101) dcScript Run Script

-----------------------------------------------
   Hub 00001 Crypto Utility Menu
-----------------------------------------------
0)  Exit
1)  Cipher Dump
2)  Prep Clock
40)  List deploy keys
41)  List node keys
42)  List tenant keys
45)  Copy deploy public key
50)  Init deploy keys
51)  Set node keys
52)  Set tenant keys
60)  Remove pgp key

Deployment:

kipo

Node:

00101

Password does not default, must enter, must match deployment Keyrings password.
Password (use same):

[enter the keyring password generated the first time you used Ignite]

new node sign key: NNNNNNNNNN

-----------------------------------------------
   Hub 00001 Crypto Utility Menu
-----------------------------------------------
0)  Exit
1)  Cipher Dump
2)  Prep Clock
40)  List deploy keys
41)  List node keys
42)  List tenant keys
45)  Copy deploy public key
50)  Init deploy keys
51)  Set node keys
52)  Set tenant keys
60)  Remove pgp key

[list your deployment keys to ensure the node shows]

Deployment: kipo

Encryptor keys (public):
 - 1392c8ad0063e0bbce06552e1da0065ea55221f0 : encryptor@kipo.dc
 - cc8a5c526de23946845c56aa2e618e062cbdf675 : ignite@kipo.dc
 - d9b9595654454f1d41cf3f0c8247ff27b2d0f29b : 99999-signer@kipo.dc
 - e750af64af8a652aad5144cee9bb363e388f51f9 : 00100-signer@kipo.dc
 - 662e524c52b05a8913bafbdf04094776fcf12e41 : root-secure@kipo.dc
 - 250b48eb7b58f9bdf4874ac0c6ea1af14ec1ab5e : kipo-secure@kipo.dc
 - b67546fa351596b3124295af5885c7645b27b740 : 00101-signer@kipo.dc

Encryptor keys (secret):
 - 1392c8ad0063e0bbce06552e1da0065ea55221f0 : encryptor@kipo.dc

Ignite keys:
 - cc8a5c526de23946845c56aa2e618e062cbdf675 : ignite@kipo.dc

Ignite keys (secret):
 - cc8a5c526de23946845c56aa2e618e062cbdf675 : ignite@kipo.dc

-----------------------------------------------
   Hub 00001 Crypto Utility Menu
-----------------------------------------------
0)  Exit
1)  Cipher Dump
2)  Prep Clock
40)  List deploy keys
41)  List node keys
42)  List tenant keys
45)  Copy deploy public key
50)  Init deploy keys
51)  Set node keys
52)  Set tenant keys
60)  Remove pgp key

-----------------------------------------------
   Hub General Utils
-----------------------------------------------
0)   Exit
1)   dcDatabase Utils
2)   Local Utilities
3)   Crypto Utilities
100) dcScript GUI Debugger
101) dcScript Run Script

-----------------------------------------------
   dcIGNITE main menu
-----------------------------------------------
0)   Exit
1)   Add Deployment
20)  Hub Utilities

Waiting on tasks!
20220430T135150064Z 000000000000004 M03 Ending session: 00001_j2fq7jvr9oguqc65mrgcuiaeul
20220430T135150064Z 000000000000004 M03 Stopping Application Server
20220430T135150073Z 000000000000004 M03 |OpId|00001-20220430T134241193Z-000000000000005| New operation context
20220430T135150074Z 000000000000005 M03 Hub entered Stopping state
20220430T135150074Z 000000000000005 M03 Hub entered Stopping state
20220430T135150075Z 000000000000005 B   |Origin|hub:|Op|Stop|
20220430T135150075Z 000000000000005 M03 Stopping hub
20220430T135150080Z 000000000000005 M03 Hub stopped
20220430T135150081Z 000000000000005 M03 Hub entered Stopped state
20220430T135150081Z 000000000000004 M03 Application hub shutdown started
20220430T135150088Z 000000000000004 M03 Application hub shutdown completed

Commit the updates to the matrix.xml and keyrings and push to the repo.

Clone the repo to another location - on your second computer or with for your teammate.

For the new location repeat the steps:

Initialize the Node's Database

Run this the same only use the new node id. For example:

$ ./foreground.sh kipo 00101 init-node

The Global Root Password and Root User Email do not have to be the same as they were on the other computer. Each Node may have its own root access.

After entering your email address, be sure to use the new node id:

Node:

00101

Add a Website (aka tenant)

Same as before, only with the new node id

$ ./foreground.sh kipo 00101

There will be fewer prompts for this part.

Configure the Host Name

Same as before.

The test has already been coded so now test it.

Test the Site

Same as before except with the new node number.

$ ./foreground.sh kipo 00101

And open the website:

http://l-kipo.com:8080/

Going Live (Production)

Instructions for production installs are available in the Server Set Up guide.