> For the complete documentation index, see [llms.txt](https://dgtnetwork.gitbook.io/dgt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.2-dgt-core-single-node-setup/6.2.1-launch-the-first-dgt-node.md).

# 6.2.1 Launch the First DGT Node

This given installation process describes the necessary steps to deploy a single node. The description is for the CORE configuration but can be adapted to work with other versions (See GARANASKA Setup below)

* First, you need to obtain the system’s source code from GitHub. DGT has [several repositories on GitHub](https://github.com/DGT-Network), each of which corresponds to a certain version of the platform – see [1.4.1](/dgt-docs/1.-introduction/1.4-the-dgt-overview/1.4.1-platform-approach.md). Please use the last version. This description is provided for the Matagami version in its CORE configuration. To start working, we clone the GitHub repository:

```
git clone https://github.com/DGT-Network/DGT-Matagami
```

As a result of execution, the DGT Matagami/CORE directory is created on the user’s home folder (HOME/DGT), from which the server image is built.

* Go to the appropriate folder and make sure the files are there:

```
cd DGT-Matagami
cd CORE
```

As a result of deploying a node, some of the general settings will be copied into the node’s configuration. To edit them and add more settings:

* Access the directory with the system settings:

```
cd DGT-Matagami/CORE/etc
```

* Set up the parameters of the node’s certificate, which will be created when connecting to the network. For that, edit the parameters of the `certificate.json` file, setting up the correct names for the administrator’s country, region, and e-mail. To connect to private segments, you must ledger these parameters:

```
nano certificate.json
```

<figure><img src="https://3210145376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSvanFNAf6Jf8kwvqcdRQ%2Fuploads%2F8sx6QIjWCTo9tS7odGJI%2Fimage.png?alt=media&amp;token=09bcca0d-9115-476d-a10b-2e9bdacad20d" alt=""><figcaption><p><em>Figure 111  certificate.json adjusting</em></p></figcaption></figure>

* Edit the network’s parameters (dgt.net.map, dgt.conf.static, entry\_points.json) – see [6.6](/dgt-docs/6.-administrator-guide/6.6-garanaska-financial-processing.md) (skip this step if setting up a single node).

After defining the settings, move towards building the node’s image.

* We carry out the initial assembly of the node using Docker Compose. Run the assembly (rise) command from the directory in which the assembly is placed (DGT/DGT-Matagami/CORE):

```
bash upDgtCluster.sh  -G -SC -CB openssl 1 1
```

Here

\-          -G – flag, indicating the need to create a genesis block

\-          -SC – flag indicating that transactions need to be signed by nodes

\-          -CB openssl – the selected type of cryptography (should be consistent with the network that the node belongs to): options are - openssl or bitcoin

\-          1 1 – cluster number and node number in the cluster; for a single node we set “1 1”. Te mapping of the number to a variant notation using segments and clusters is reflected in the dgt.net.map file.

&#x20;The assembly process is quite long, accompanied by the installation of additional packages. A typical output is shown in the figure below:

<figure><img src="https://3210145376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSvanFNAf6Jf8kwvqcdRQ%2Fuploads%2Ff8tyuR0NiTJO3lk8TYLE%2Fimage.png?alt=media&amp;token=d2e8a733-cdb8-4200-b8d0-6d15748c4c85" alt=""><figcaption><p><em>Figure 112 First Building for Single Node</em></p></figcaption></figure>

{% hint style="info" %}
The full assembly process is conducted only when updating the home directory of the project (DGT-Matagami/CORE). Afterwards, a simplified process of launching the relevant container is conducted.
{% endhint %}