The serverside prerendering works in theory. The recording is just 2-4 Megabytes and the playback on the frontend consumes nearly no additional computing resources.
The little problem is that prerendering is kind of ultra heavy :-D
My Raspi 3 takes more than a minute for that (with only a few additional modules running) and takes >60MB memory for that.
For those of you having problems due to limited resources with live rendering, the prerendering won’t be the answer I guess :-/

I have a alpha version for a backend-generated (pre-rendered) map.
Are there any volunteers who would like to test it? (Please only people who can withstand high frustration :-D )

I think about pre-rendering the map animation once as gif image in the backend using phantom instead of live rendering on the frontend. I’ll test that when time allows…

@Stoffbeuteluwe nope, the data provider only serves weather history

@retroflex yes. It now supports both.
Find the information regarding config on GitHub.

@retroflex because my girlfriend didn’t like the vocabulary :-D

I fixed the timeFormat error. Thank you for your feedback @chassain-0

Module deleted

Does anyone else have the problem? I can’t reproduce it anymore.

The memory problem should hopefully be fixed.