You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
InfoMark is an is a scalable, modern and open-source [rewrite of our](https://github.com/cgtuebingen/InfoMark-deprecated) online course management system with auto testing of students submissions [(video)](https://www.youtube.com/watch?v=ifyUssK6PJ4) to ease the task of TAs.
10
+
InfoMark is an is a scalable, modern and open-source [rewrite of our](https://github.com/infomark-org/InfoMark-deprecated) online course management system with auto testing of students submissions [(video)](https://www.youtube.com/watch?v=ifyUssK6PJ4) to ease the task of TAs.
11
11
12
12
13
13
See [https://infomark.org](https://infomark.org) for more details.
Copy file name to clipboardExpand all lines: docs/content/guides/administrator.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ worker_workdir: /tmp
36
36
...
37
37
```
38
38
39
-
For an example configuration please refer to the `.infomark.example.yml` your downloaded release archive or inspect the file [on GitHub](https://github.com/cgtuebingen/infomark-backend/blob/master/.infomark.example.yml).
39
+
For an example configuration please refer to the `.infomark.example.yml` your downloaded release archive or inspect the file [on GitHub](https://github.com/infomark-org/infomark-backend/blob/master/.infomark.example.yml).
40
40
41
41
Only the keys `rabbitmq_*` need to be shared between the server. In general, the defaults might do the job. For all secrets like passwords, tokens or keys you should use `openssl rand -base64 32` to generate random high-quality secrets.
42
42
@@ -284,4 +284,4 @@ The definition of all available routes to the RESTful backend is described in ou
284
284
285
285
The metrics for [Prometheus](https://prometheus.io/) are served under `localhost:<port>/metrics`. We highly suggest not to expose these metrics when using a reverse proxy like NGINX.
286
286
287
-
To visualize these metrics we have assembled a [custom Grafana-Board](https://github.com/cgtuebingen/infomark/tree/master/metrics).
287
+
To visualize these metrics we have assembled a [custom Grafana-Board](https://github.com/infomark-org/infomark/tree/master/metrics).
Copy file name to clipboardExpand all lines: docs/content/guides/developer.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,14 +9,14 @@ The System is managed via two git-repositories.
9
9
Both parts are tested separately using continuous integration tests. It is a good idea to read the `.drone.yml` configuration on how to build these parts from source.
10
10
11
11
Whenever a combination is stable, we will create a new release, which can be downloaded here:
wget -qO- https://github.com/infomark-org/infomark/releases/download/${VERSION}/infomark.tar.gz | tar -xzv
23
23
24
24
cd infomark
25
25
cp .infomark.example.yml .infomark.yml
@@ -85,8 +85,8 @@ We use continuous-integration tests to ensure the implementation can be built an
85
85
At its core, InfoMark is a single-compiled Go binary that is exposed as a Restful JSON web server with Javascript clients. See the Restful API docs (created using [Swagger](https://swagger.io/)) [here](https://infomark.org/swagger/).
The backend acts as a Restful JSON web server and is written in [Go](https://golang.org/). All dependencies are encapsulated in a docker-compose configuration file. The dependencies are:
92
92
@@ -131,8 +131,8 @@ To avoid manual interaction with the database InfoMark provides a console to run
The frontend is written in [Elm](https://elm-lang.org/), a functional frontend language which compiles to JavaScript. The application is just a single page application (SPA) which uses fragments for
138
138
routing. So the server only needs to distribute the static HTML page and the REST API which is used to
as an entry point. Please either use [one of our pre-defined test-examples](https://github.com/cgtuebingen/infomark/tree/master/unittests) or create your own.
51
+
as an entry point. Please either use [one of our pre-defined test-examples](https://github.com/infomark-org/infomark/tree/master/unittests) or create your own.
52
52
By design we assume, that
53
53
54
54
* The testing-framework, e.g., JUnit, ensures that all stdout from the uploaded user code is suppressed.
@@ -62,22 +62,22 @@ There are some ways to ease the task of writing unit-tests.
62
62
A clear directory structure and a Makefile to automatically pack all necessary archives or/and run the unit-test locally can dramatically speed up the entire process and avoid debugging steps on the server.
63
63
64
64
The *makefile* should be able to clean temporary files, zip files and simulate the test result locally using the correct docker-image.
65
-
Further, specifying the docker-image in the *makefile* helps to set up the task in InfoMark as you will need to specify it there while creating a new exercise task. An [example-Makefile](https://github.com/cgtuebingen/infomark/blob/master/unittests/python/makefile) is given in our repository.
65
+
Further, specifying the docker-image in the *makefile* helps to set up the task in InfoMark as you will need to specify it there while creating a new exercise task. An [example-Makefile](https://github.com/infomark-org/infomark/blob/master/unittests/python/makefile) is given in our repository.
66
66
67
67
InfoMark is language-agnostic. The system only records the docker-output. All post-processing of runs (processing JUNIT outputs) must be done *within* the docker container.
68
68
69
69
We provide several testing-templates and examples
70
70
71
71
| language | dockerimage (hub.docker.com) | test example | dockerfile |
| C++ |[patwie/test_cpp_submission:latest](https://hub.docker.com/r/patwie/test_cpp_submission)|[yes](https://github.com/cgtuebingen/infomark/tree/master/unittests/cpp)|[yes](https://github.com/cgtuebingen/infomark/tree/master/dockerimages/unittests/cpp)|
| C++ |[patwie/test_cpp_submission:latest](https://hub.docker.com/r/patwie/test_cpp_submission)|[yes](https://github.com/infomark-org/infomark/tree/master/unittests/cpp)|[yes](https://github.com/infomark-org/infomark/tree/master/dockerimages/unittests/cpp)|
76
76
77
77
78
78
## Java 11
79
79
80
-
We suggest using our [docker-image](https://github.com/cgtuebingen/infomark/tree/master/dockerimages/unittests) to run follow the guide below.
80
+
We suggest using our [docker-image](https://github.com/infomark-org/infomark/tree/master/dockerimages/unittests) to run follow the guide below.
81
81
82
82
We use the following directory structure to reduce the workload of writing re-usable unit-tests.
83
83
@@ -109,7 +109,7 @@ exercises
109
109
build.xml
110
110
```
111
111
112
-
where `[a.b]` represents the exercise-task-number. A working example can be found in the [InfoMark-repository](https://github.com/cgtuebingen/infomark/tree/master/unittests).
112
+
where `[a.b]` represents the exercise-task-number. A working example can be found in the [InfoMark-repository](https://github.com/infomark-org/infomark/tree/master/unittests).
113
113
114
114
### Student-Template
115
115
@@ -158,7 +158,7 @@ We suggest to have two sub-types of tests:
158
158
- Structure-Tests
159
159
- Value-Tests
160
160
161
-
We have composed a [Helper.java](https://github.com/cgtuebingen/infomark/blob/master/unittests/java/unittest_private_0.1/src/__unittest/Helper.java) file to ease the work with reflections when checking the solutions of the exercise tasks.
161
+
We have composed a [Helper.java](https://github.com/infomark-org/infomark/blob/master/unittests/java/unittest_private_0.1/src/__unittest/Helper.java) file to ease the work with reflections when checking the solutions of the exercise tasks.
162
162
163
163
The overall structure should be
164
164
@@ -283,7 +283,7 @@ A good candidate for a private test would be
283
283
284
284
## Python 3
285
285
286
-
We provide the a very basic but working test set for checking python programming assignment solutions in our [git-repository](https://github.com/cgtuebingen/infomark/tree/master/unittests/python).
286
+
We provide the a very basic but working test set for checking python programming assignment solutions in our [git-repository](https://github.com/infomark-org/infomark/tree/master/unittests/python).
287
287
288
288
The basic idea is that any upload will be unzipped into a directory together with the unit-test:
289
289
@@ -348,7 +348,7 @@ FAILED (failures=1)
348
348
349
349
## C++
350
350
351
-
Testing in C++ is a bit tricky, doing reflections is difficult. A basic example is provided in out [git-repository](https://github.com/cgtuebingen/infomark/tree/master/unittests/cpp).
351
+
Testing in C++ is a bit tricky, doing reflections is difficult. A basic example is provided in out [git-repository](https://github.com/infomark-org/infomark/tree/master/unittests/cpp).
352
352
The final directory structure *inside* the docker container will be
0 commit comments