ASWI - Pokročilé softwarové inženýrství » ASWI 2021 » OpenData vlastní téma (KIV) - Tři Mušketýři

h1. Server Installation (WIP)

The server runs on Debian 10 VM at https://nuada.zcu.cz/

The ip of the machine is 147.228.173.54

h2. Hardware requirements

TBD, however the default settings for creating the VM seem to suffice

h2. Software requirements

h2. "Deploying" the Server Application

h3. Uploading the project to the remote machine

Upload the whole folder built with the commands below:

<pre>

scp -r /pathToFolder/publish root@{machine_ip}:/<path>/

</pre>

You can also upload the default configuration file:

<pre>

scp /path/server_config root@{machine_ip}:/<path>/

</pre>

h3. Building the project

At the moment, the easiest way to build the project is to build it locally in Windows with the following commands:

open windows command line (cmd.exe) in the directory where the solution file is located. Please make sure you can run `dotnet` command from the cmd. Make sure you have the right SDK on your system:

<pre>

dotnet --list-sdks

</pre>

Version 5.0 is needed to build the project. If you have this version, you can build the project:

<pre>

dotnet publish --runtime=linux-x64 ServerApp.sln

</pre>

The built project files are in folder:

.\ServerApp\bin\Debug\net5.0\linux-x64\publish

h3. Note

The project could probably be built on-site as well, but that would require .NET SDK to be installed and require larger disc space.

h3. Running the server

* A folder named *data* must exist in the directory where the app is launched

* A .p12 file named *cert.p12* must exist in the directory where the app is launched

** We used this one: attachment:cert.p12

Firstly you most grant permission to run the executable:

<pre>

chmod +x <path>/ServerApp

</pre>

Then you can run the server:

<pre>

<path>/ServerApp <args>

</pre>

---

h3. Certificate generation and usage (DEPRECATED)

This section provides instructions for generating and using a certificate with a secific port.

*Important note*: this approach was used when the server application ran under the Mono framework. Mono is no longer used for running the application as it was unable to use some needed libraries.

* Follow these steps if the above stated instructions didn't work as expected.

h4. Mono installation

<pre>

sudo apt install mono-complete

</pre>

h4. Generating the certificate

http://www.mono-project.com/archived/using-clientcertificates-with-xsp/

<pre>

makecert -r -n "CN=My Own Test CA" -sv root.key root.cer

certmgr --add -c Trust root.cer

hostname (displays the machine's host name)

makecert -iv root.key -ic root.cer -eku 1.3.6.1.5.5.7.3.1 -n "CN={hostname}" -p12 {hostname}.p12 s3kr3t

</pre>

h4. Linking the certificate to a port?

<pre>

httpcfg -add -port {port} -pvk root.key -cert root.crt

</pre>

h4. Adding trusted root certificates to the server (idk if this has any effect)

Copy your CA to dir /usr/local/share/ca-certificates/

Use command: sudo cp foo.crt /usr/local/share/ca-certificates/foo.crt

Update the CA store: sudo update-ca-certificates

---