The ChirpStack installation will be very fast. 1
Whatever the hardware we've chosen to install the server, 2
the fact that we use a Docker container will make it very easy. For us, 3
it's time now to choose where we will set up our server. 4
We've seen many possible options. 5
It can be our local PC, a Raspberry Pi, a virtual machine, but in my case I'm going to use a public 6
server that I've rented from a cloud provider. 7
It's a simple machine with very few capabilities: 2 Giga Bytes of RAM and only one virtual Core. 8
But it will be more than enough for our demonstration. 9
Of course, as our network increases because for example we have new clients, then we can scale 10
it to increase its capacity. 11
If you've chosen to set up your server on another platform, no problem, 12
the demonstration will exactly be the same. 13
So, no worries. On my server, 14
I've installed a Basic Linux Debian Operating System. 15
Actually, to be honest I haven't done it myself 16
as my server provider propose many ready to use operating system and I picked up debian. And, the only 17
thing I've installed is as we've said several times, Docker and Docker-compose. 18
In addition to this private server, 19
I also have a domain name. 20
So if we want, instead of using the server IP address we can use the URL chirpstack.univ-lorawan.fr. 21
It's not compulsory, but I reckon it's clearer and more convenient. 22
If you only have an IP address available then no worries, 23
you can obviously use it. 24
So for this demonstration I connect to my Linux machine using SSH. 25
If you don't remember how to connect a remote machine using SSH, then please see the specific video 26
in the HOW TO section at the beginning of this course. 27
Here we go. 28
I've got a terminal from my remote Linux. 29
Okay. 30
Now if we look at the ChirpStack documentation. 31
Basically, the installation process is composed of three steps. 32
First, we need to download the ChirpStack container configuration file called docker-compose.yml. 33
We will also need the other configuration file that Docker will use to build the LoRaWAN server as it's 34
an open source server. 35
All these files are on the ChirpStack GitHub repository. 36
This step is easy. In ChirpStack documentation, 37
they provide the right command to download all files. 38
We just need to use it. 39
git clone and the repository address. 40
Then we enter the downloaded folder. 41
Right. 42
Now that we have all the necessary files, the second step is to apply our specific configuration. 43
We could configure the credentials to connect to the LoRaWAN server. 44
We could enable or disable some region, but in our case that's going to be extremely easy because if 45
we leave the default values, these default configuration works out of the box. 46
Great. 47
So, let's launch the installation process. 48
We just need to use the command docker compose up. 49
I'm just going to add two things in the command. 50
First, the keyword sudo, because I use a Linux environment and I need to ask for privileges to execute 51
the docker compose command. 52
Secondly, I'm using the option -d because I want to leave ChirpStack running in the background, 53
otherwise I wouldn't be able to get my terminal back. 54
Okay, let's try that. 55
It takes a few seconds. 56
All containers are downloaded, extracted and created and my ChirpStack server is now ready. 57
It's not more complicated than that. 58
Now, we have all services running. 59
We can check them with another command. 60
docker ps. 61
There we go. 62
Everything is up and running. By default on ChirpStack, 63
if we want to have access to the user interface, then we need to use a web browser with the server 64
URL on port 8080. 65
But of course I could have used the IP address. 66
Okay, great. 67
And the default login and password is admin/admin and we are now logged on our new Network Server. As 68
it's a public server, 69
the first thing we need to do is obviously to update our password. 70
Okay. 71
Now that the installation process is done, let's present the ChirpStack network server interface. 72
On the left, the user interface has a menu with two parts. 73
On the top, it's the administrator menu. 74
It means that it's only available if we have privileges. 75
It's called the network server menu and of course we can access it because we have the administrator 76
login. 77
In this menu, we can configure the tenant, users and many other network properties. 78
There is already one tenant available by default. 79
It's called ChirpStack. 80
A tenant is a group of users and for each group, so for each tenant we can decide the number of gateways 81
and the number of devices it can register. 82
So, of course we can create another tenant. 83
And below, there is the number of gateway and devices the Network Server administrator will allow for 84
this tenant. 85
We can also change it later if we need to update some privileges to a specific tenant. 86
Okay. 87
In my case, I'm not going to add a new tenant to the list because for this demonstration we'll keep 88
the default value one called ChirpStack. 89
If we select a specific tenant. 90
So in our case ChirpStack, as it's the only one available, then we'll be able to create users. 91
In my case, I use the administrator login, so I don't need to create users. 92
But if you're a company and need several accounts on this server, then you will need to create as many 93
users as you want and assign specific rights and privileges. 94
Great. 95
Now, with the bottom menu, we'll be able to complete the usual process to register gateways, applications 96
and end-devices. 97
And that's what we're going to do in the next video.