Skip to content

Commit 83708a0

Browse files
committed
Automatic release of teaching material.
1 parent 7ababa1 commit 83708a0

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

README.adoc

+4-1
Original file line numberDiff line numberDiff line change
@@ -171,8 +171,11 @@ TBA
171171
=== Dashboards
172172

173173
==== Activity Dashboard
174+
* link:http://138.68.66.124/status.html[Overview]
175+
* link:http://138.68.66.124/commit_activity_daily.svg[Daily commit activity per group]
176+
* link:http://138.68.66.124/commit_activity_weekly.svg[Weekly commit activity per group]
177+
* link:http://138.68.66.124/release_activity_weekly.svg[Weekly release activity per group]
174178

175-
TBA
176179

177180
==== Simulator Status Dashboard
178181

sessions/session_03/README_TASKS.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You can find the (*implicit*) specification for the simulator API in
1919
- Provide **the same HTTP status codes** in response as specified.
2020

2121

22-
The [`API_Spec/minitwit_sim_api.py`](./API_Spec/minitwit_sim_api_test.py) depends on your refactored `minitwit.py` from last week's homework.
22+
The [`API_Spec/minitwit_sim_api.py`](./API_Spec/minitwit_sim_api_test.py) depends on your refactored `minitwit.py` from last week's homework.
2323

2424
A corresponding test ([`API_Spec/minitwit_sim_api_test.py`](./API_Spec/minitwit_sim_api_test.py)) illustrates how the simulator requests will be formed. You can inspect it and run it via `pytest minitwit_sim_api_test.py`.
2525
(`pytest` can be installed via `pip`)
@@ -56,7 +56,7 @@ Continue refactoring of your version of _ITU-MiniTwit_ with missing features and
5656

5757
* Make your development environment and deployment environment "look alike". That is, you develop on an Ubuntu 22.04 based Linux (Pop!_OS), choose the same environment for your remote server(s).
5858

59-
* **Hint**: To make future operations more smooth, you might **consider to use a [floating IP](https://docs.digitalocean.com/products/networking/floating-ips/) 'infront' of your actual server**, see the [API spec.](https://docs.digitalocean.com/reference/api/api-reference/#tag/Floating-IPs) for receiving one.
59+
* **Hint**: To make future operations more smooth, you might **consider to use a [floating IP](https://docs.digitalocean.com/products/networking/floating-ips/) 'infront' of your actual server**, see the [API spec.](https://docs.digitalocean.com/reference/api/digitalocean/#tag/Floating-IPs) for receiving one.
6060

6161

6262
**OBS MSc students**: Remember to log and provide good arguments for the choice of virtualization techniques and deployment targets.

0 commit comments

Comments
 (0)