Rationale: if one build fails, the other one will still continue running.
Especially since we already have some (and will presumably add more)
proprietary software to nixda which may require manual intervention
using nix-prefetch-url, this seems like a good idea.
An alternative would be to just specifiy `--keep-going`, but this seems
likely to lead to unreadable output.
However, I'm not sure what exactly happens when we try to run builds for
both hosts at once on the same nix store — it may be that this isn't the
best idea, but I guess we can just make the pipelines sequential instead
if necessary.
pipeline: fix mistake in build command
(previous commit contained two builds for nixda, none for hainich)
Assuming I've understood the format of this config correctly, this
should add two new addresses for the c3wooc (one for general contact,
one for patches); both forwarding to its members (currently only hxchn
and me).
Changes:
- workadventure is now pulled from stuebinm.eu/git via niv, and
should be updated automatically along with the other sources
- the same is true for the default map, which gets pulled directly from
its gitlab sources.
- this setup may potentially break things if I decide to rename an
option upstream, but I don't think that'll happen too often
- made the code a little nicer
- uses workadventure-xce now, since the tabascoeye version is now gone
Open for discussion:
- afaik know, the current version of workadventure-xce now contains
fediventure-specific patches. Do we want that, or should we switch
to the unfederated version?
this is a workaround to be able to use java 11 with the
minecraft-server module
minecraft calls for jre_headless, which is still java 8
newer java version don't ship jre, which now have to be custom built or
the jdk used
note that this ALSO disables the security alert features of mattermost [1],
which would send us alerts in case of security updates for our current
mattermost version. I have disabled it since it would send information
about our instance (including e.g. the current number of active users) to
mattermost every 24 hours.
Since we now essentially maintain our own set of mattermost packages, I
recommend at least some of us subscribe to the mattermost release blog [2],
and manually update the mattermost sources in `/pkgs/mattermost` as required
(I have done so already). The release blog is also available as an rss feed [3].
[1] https://docs.mattermost.com/administration/telemetry.html#security-update-check-feature
[2] https://mattermost.com/blog/category/releases
[3] https://mattermost.com/blog/category/releases/rss
stuebinm
hexchen