How to deploy

The deployment method in simple terms is that the user runs the deploy trigger script in order to send a SSH-command to the server, this command will then trigger the deploy script locally on the server machine. The deploy script in its current stage will perform an update to the server, pull from the main branch of the repository, and perform a rebuild of the project. Since the output of the process is local to the server it will create a log file of the entire process.

Important

In order to run the deploy trigger you must have acuired the SSH-key.

1. Change the path to your local SSH-file.

The deploy trigger script is located here: BoundlessFlowCampus2K/src/branch/main/scripts/deployment/DeployTrigger.sh

Before running the script, change the path /path/to/key/private.key in the script to point to your local SSH-key.

2. Run the scripts.

Run the script by entering the command in the terminal from the deployment directory.

sudo sh DeployTrigger.sh

3. Verify the deployment.

1. SSH into the server by the command (Note that private.key is the path to SSH-key):

sudo ssh -i private.key -p 2222 ubuntu@193.93.250.90

2. Change directory to the logging directory:

cd /DeploymentBFC2k/BoundlessFlowCampus2K/scripts/deployment/logs

3. Open the most recently changed logfile with Nano:

nano "$(git ls-files | xargs ls -t | head -n1)"

The end of the logfile should look something like this, confirming that the script was run succesfully.

[2026-05-08_11:25:31] Running docker status
CONTAINER ID   IMAGE                            COMMAND                  CREATED          STATUS                             PORTS                    NAMES
1648357d7038   middleware                       "dotnet middleware.d…"   30 seconds ago   Up 3 seconds                                                middl>
b667341aacc9   entrypoint                       "/docker-entrypoint.…"   30 seconds ago   Up 1 second                        0.0.0.0:80->80/tcp       entry>
e0ea05d358d2   eclipse-mosquitto:2.1.2-alpine   "/docker-entrypoint.…"   37 seconds ago   Up 13 seconds (healthy)            1883/tcp                 mosqu>
84c0f444005b   energyservice                    "dotnet energyServic…"   37 seconds ago   Up 5 seconds                                                energ>
d040c9116b51   tempservice                      "dotnet tempService.…"   37 seconds ago   Up 6 seconds                                                tempS>
4220086967c4   loginservice                     "dotnet loginService…"   37 seconds ago   Up 4 seconds                                                login>
8103dceb20c0   roombookingapimockup             "dotnet roomBookingA…"   37 seconds ago   Up 4 seconds                                                roomB>
1ddbf4e05e3e   layoutservice                    "dotnet layoutServic…"   37 seconds ago   Up 20 seconds                                               layou>
e06f80ba5023   readenergysensor                 "dotnet readEnergySe…"   37 seconds ago   Up 14 seconds                                               readE>
105f500be7bc   parkingapimockup                 "dotnet ParkingApiMo…"   37 seconds ago   Up 4 seconds                       0.0.0.0:1212->1212/tcp   parki>
7e78a0555c9b   parkingbookingdbhandler          "dotnet ParkingBooki…"   37 seconds ago   Up 14 seconds                                               parki>
098d1f7eb324   postgres:18.3-alpine3.23         "docker-entrypoint.s…"   51 seconds ago   Up 25 seconds (healthy)            5432/tcp                 Postg>
99fa6205ae1f   frontend                         "/docker-entrypoint.…"   52 seconds ago   Up 25 seconds (health: starting)   0.0.0.0:3000->80/tcp     front>
bcf891180e28   readtempsensormockup             "dotnet readTempSens…"   52 seconds ago   Up 10 seconds                                               readT>
388dd48dcb1d   energysensormockup               "dotnet energySensor…"   52 seconds ago   Up 26 seconds                                               energ>
fada226b1e56   tempsensormockup                 "dotnet tempSensorMo…"   52 seconds ago   Up 25 seconds                      8080/tcp                 tempS>
[2026-05-08_11:25:31] The deployment script was executed succesfully!

If everything worked out in the description you have succesfully deployed to the web server.