Misterver Portainer Docker installation

[Jens Neubieser]

Hello

I just can't get the Mistserver to retain its configuration when I regenerate the container in Portainer.

Could someone send me a complete stack showing how to create the Mistserver, including persistent directories on the server where the configuration, videos, and logs are stored?

Thanks in advance.

Jen

[jammin radio]

Windows or Linux 

--
You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mistserver/a459355d-c09e-4fb6-9eed-4e58dcd571d1n%40googlegroups.com.

[Jens Neubieser]

Linux (Ubuntu)

[jammin radio]

I had issues - then I used Debian 

FRESH install update system 

Ngix proxy manager for SSL 

Azuracast for radio stations 

Then I installed mistserver 

I use separate HTTP for each clients streams 

& a separate url for admin 

System runs faultless 

To view this discussion visit https://groups.google.com/d/msgid/mistserver/8e408667-2b6a-4cab-9063-53a5ed1f5cb1n%40googlegroups.com.

[Jens Neubieser]

In which directory is the configuration file config.json stored by the mistserver?

[jammin radio]

I used the mist install script so 

To view this discussion visit https://groups.google.com/d/msgid/mistserver/b360bd59-096e-4da6-8a3b-83a4a44c3654n%40googlegroups.com.

[Michel Hageman]

This is the config that I use too, as a basis. In here are also the two volumes you need to keep the settings in the container. 

services:

    mistserver:

        image: ddvtech/mistserver_alpine_minimal

        container_name: mistserver

        volumes:

          - /PATH/TO/CONFIG/config.json:/config.json

          - /PATH/TO/VIDEOFOLDER:/video

        shm_size: '2gb'

        network_mode: 'host'

        restart: always

You can find more here: 

https://docs.mistserver.org/mistserver/installation/docker/

Hope this will work out for you. 

To view this discussion visit https://groups.google.com/d/msgid/mistserver/CAD%3DndbkA6S9rYvXDxKmoB_qJ%3DctW4vPxyO7th63BFU37vjoXUA%40mail.gmail.com.

[Balder Vietor]

Hey!

Losing configurations generally means that the config that was stored simply isn't re-used. This could be because you've set things up that it starts a new "clean" run every time, or because you're trying to save the configurations to a place where your Docker isn't allowed to store. 

I would indeed recommend linking the config to a file outside of Docker so you can re-use (or edit) it easily. If MistServer is ran without any boot commands it's indeed `config.json` in the same folder as MistController. If the install script is used you'll need to link it to `/etc/mistserver.conf`. The guide linked ( https://docs.mistserver.org/mistserver/installation/docker/ ) should indeed contain most of what you need.

We are working on a more complete Docker stack here: https://github.com/DDVTECH/mistserver-bootstrap

Bear in mind this is still a work in progress, so some settings might be off or need tweaking, but it will most likely give you a more complete example. It's meant to activate a few more things within MistServer, such as the encoder based on libAV and automatically add prometheus/grafana for analytics. 

I would definitely recommend increasing shared memory depending on how heavy your usage will be, since MistServer does rely on it quite heavily. You'll need at least enough to hold the stream buffer for every stream (live or vod) and ~2mb extra for every viewer. 

Regards,

Balder

[Michel Hageman]

Thanks Balder,

I'll check out the new Docket setup, because I'm very interested in this.

Thanks again, also for your reply to the OP, which is helpful! 

Greetings,

Michel

To view this discussion visit https://groups.google.com/d/msgid/mistserver/b09414ef-6500-4c8c-96d2-66fbb42713aan%40googlegroups.com.

[Balder Vietor]

You're welcome, and of course also to the others, pretty solid tips were given!

Figured I'd add this little tidbit as well, since we've flagged this as problematic during testing yesterday:

The creation of the docker compose often fails because of a connection issue to the RIST code hosted at https://code.videolan.org/rist/librist . Retrying multiple times "eventually" goes through, but we're considering adding the compile flag `-DNORIST=true` to the process to disable it and avoid this and have builds succeed far more often.

Downside would be that there's no RIST support in that case, so it's not a very happy solution. Currently we plan to just do more from scratch tests to see if yesterday was just a "bad day" for 3 of our machines.

Regards,

Balder