chvp/phd-thesis
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Small textual changes

Browse source
This commit is contained in:
Charlotte Van Petegem 2024-01-17 15:31:08 +01:00
parent e3f1c447f6
commit 36857a1ab8
No known key found for this signature in database
GPG key ID: 019E764B7184435A
1 changed files with 2 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
book.org
View file

@ -770,7 +770,7 @@ The TESTed judge came forth out of a prototype I built in my master's thesis\nbs
To ensure that Dodona is robust to sudden increases in workload and when serving hundreds of concurrent users, it has a multi-tier service architecture that delegates different parts of the application to different servers, as can be seen on figure\nbsp{}[[fig:technicaldodonaservers]].
More specifically, the web server, database (MySQL) and caching system (Memcached) each run on their own machine.
In addition, a scalable pool of interchangeable worker servers are available to automatically assess incoming student submissions.
In this section, I will highlight the workings of a few of these components.
In this section, I will highlight a few of these components.
#+CAPTION: Diagram of all the servers involved with running and developing Dodona.
#+CAPTION: Every server also has an implicit connection with Phocus (the monitoring server), since metrics are collected on every server such as load, CPU usage, disk usage, ...
@ -786,7 +786,7 @@ In this section, I will highlight the workings of a few of these components.
The user-facing part of Dodona runs on the main web server, also called Dodona (see figure\nbsp{}[[fig:technicaldodonaservers]]).
Dodona is a Ruby-on-Rails web application, following the Rails-standard way of organizing functionality in models, views and controllers.
The way we handle complex logic in the frontend has seen a number of changes along the years.
The changes were mostly done because of increasing complexity and to eliminate jQuery.
These changes were mostly done because of increasing complexity and to eliminate jQuery.
When Dodona was started, there were only a few places where JavaScript was used.
Dodona also used the Rails-standard way of serving dynamically generated JavaScript to replace parts of pages (e.g. for pagination or search).
With the introduction of more complex features like evaluations, we switch to using lightweight web components where this made sense.
@ -913,7 +913,6 @@ When we did versioned releases we also wrote release notes at that point.
Because we don't have versioned releases any more, we now bundle the changes into release notes for every month.
They are mostly autogenerated from the merged PRs, but bigger features are given more context and explanation.
*** Deployment process
:PROPERTIES:
:CREATED: [2023-11-23 Thu 17:13]